Lately I have been getting random reboots and random black screens. The phone will either reboot itself show the galaxy s3 screen then go to complete darkness or vibrate and go straight to complete darkness. This seems to be random and usually starts happening a week or so after flashing a rom or kernel. Right now I am using my own TW rom (in dev section) with kt kernel and team kernalizer scripts. But the kernel doesn't seem to matter as this happens regardless. Does anyone know whats going on? Also this started happening after I ran aokp 4.2.2 for awhile, then odin back to stock and issues started. I've also been having less battery life since then.
Someone please help
anyone?
aamir123 said:
anyone?
Click to expand...
Click to collapse
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Aerowinder said:
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Click to expand...
Click to collapse
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
aamir123 said:
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
Click to expand...
Click to collapse
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Aerowinder said:
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Click to expand...
Click to collapse
ok I guess I'll go back but I don't see why the md5 firmware would be a problem now after I was using it with no problem for a while.
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
DocHoliday77 said:
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I flashed the LJC fw and so far it's been pretty stable, only having trouble with excess heat but will probably get better with time. Also I'm having trouble getting a logcat app running (catlog etc). The app opens I give it root permissions, then I get a black screen with loading ring. No log whatsoever, is that normal? tried on both fw btw.
just got another random reboot on ljc fw. any other ideas?
aamir123 said:
just got another random reboot on ljc fw. any other ideas?
Click to expand...
Click to collapse
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
cboss718 said:
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
Click to expand...
Click to collapse
Idk what the issue is I'm gonna go stock for a while without recovering and see if that will fix anything, if not maybe tmobile is the way to go. Btw I tried taking a log cat but get error saying that dev/log/main doesn't exist.
Ok I was doing good for a few hours after flashing stock and not restoring Google account until I got a random reboot just now. I was able to get a log cat tho so I'd anyone can look at it and help.
Sent from my SGH-T999 using xda app-developers app
anybody? Does anyonehave any ideas?
aamir123 said:
anybody? Does anyonehave any ideas?
Click to expand...
Click to collapse
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Aerowinder said:
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Click to expand...
Click to collapse
ok I will try to get that the next time it reboots. Hopefully it's a simple fix, but just not sure what the problem could be.
So I went all these days without a random reboot and finally got one today, but was unable to pull a dmesg as it said does not exist. What can I try to get a dmesg now?
Also the phone feels like it never shuts down, even when I choose to shutdown in the menu it ends up restarting itself then bootlooping or just restarting. I've also noticed that holding home and power to turn phone on works most of the time to get it back to the os only to have it crash shortly after. I press home and power until I see the white splashscreen then let power button go. but staying in os for more than a few mins right now is impossible.
Related
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
doing the same thing right now. i'm in germany so i'm not sure if that's what's causing the slow download speed 500Mbps link @ a convention center, but i'm at 416MB out of 617MB and very very very patiently waiting.
it's good to hear that you only ran into that small issue. i'll keep an eye out for it. Thanks!
ak907 said:
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
Click to expand...
Click to collapse
Welcome to XDA!
I'm downloading it on my computer at home right now but I was in a rush to get to work. Looks like I'll have to wait until my lunch break to flash this, haha.
Also I see you're from Wasilla! Enjoying the weather? (I'm originally from Fairbanks)
Maroon Mushroom said:
Welcome to XDA!
I'm downloading it on my computer at home right now but I was in a rush to get to work. Looks like I'll have to wait until my lunch break to flash this, haha.
Also I see you're from Wasilla! Enjoying the weather? (I'm originally from Fairbanks)
Click to expand...
Click to collapse
First post here as well. I was rooted on stock, and this flashed flawlessly. Not 1 problem. Thanks!
ran the update, installed cwm and the phone works flawlessly minus one issue. gaming has become laggy. anyone else with studder or lag issues?
Aww man. It figures, I just finished flashing another rom like, about 18 hours ago. Now with finals coming up, I don't have time to do this one! Oh well, I guess I have something to do AFTER finals then, hahaha.
bluemax189 said:
ran the update, installed cwm and the phone works flawlessly minus one issue. gaming has become laggy. anyone else with studder or lag issues?
Click to expand...
Click to collapse
Is your power saving mode on? I've always found it makes so many things laggy, unfortunately. Might be enabled by default on the rom. Worth a look.
Great community here. Yesterday I was non-rooted ICS. Today I'm rooted JB with Wallet.
My phone just got 1000% better.
First of all, I appreciate all the Devs hard work bringing these Roms to us! :good:
I was running rooted UCALH9. Updated to this JB via Odin and all SEEMED good. Problems I had:
1) Play Store FC's - FIX - I went into Application Manager and removed updates for the Play Store app, which reverted it back to the default Play Store app. This fixed my problem. MAKE SURE YOU DO NOT UNINSTALL!
2) Rom Manager - I would get root user authentication error when trying to Fix Permissions. Everything else in Rom Manager worked. No fix at this time.
3) Gallery - None of my pictures were showing up. This is even after clearing caches. I am convinced it's because I can't Fix Permissions, but what do I know... No fix at this time.
Any help would be appreciated!
Damn I had that same Play Store FC problem yesterday -- I wish I'd have figured that out. I ended up doing factory reset lol.
I receive same fix permission error as you, but I rebooted into recovery to do it.
egyan said:
Damn I had that same Play Store FC problem yesterday -- I wish I'd have figured that out. I ended up doing factory reset lol.
I receive same fix permission error as you, but I rebooted into recovery to do it.
Click to expand...
Click to collapse
You didn't happen to play with the camera at all, did you?
I can live with the Fix Permissions via CMW, so that would clear up 2 out of 3 of my problems. All I need is a fix for the Gallery problem, and I can go back to Official JB.
Thanks!
Howl long was the flash?
I'm inside Odin on flashing system.img.ext4 right now and it stays there which looks like about 20% for last 10 minutes with no forward movement.
How long do I need to wait before I consider something is wrong with flash process?
Changing cable to Samsung one did the trick if you are in the same situation.
Can you do this AFTER upgrading to Jellybean?
questionmillennium said:
Can you do this AFTER upgrading to Jellybean?
Click to expand...
Click to collapse
Wondering the same thing. I already installed the official JB and set all my stuff up. Will this wipe all of those settings or just simply inject the root files?
questionmillennium said:
Can you do this AFTER upgrading to Jellybean?
Click to expand...
Click to collapse
greystealth said:
Wondering the same thing. I already installed the official JB and set all my stuff up. Will this wipe all of those settings or just simply inject the root files?
Click to expand...
Click to collapse
If you are talking about flashing the root injected JB i post, yes you can flash it after upgrading and no it won't wipe anything in data, everything should be preserved for you.
Weather here sux.... Hovering slightly above 0 degrees with 80 mph winds for the last week so add on the wind chill factor and u can only imagine... And no snow yet.
So far no other issues with this rom. Seems to run perfectly. Now just waiting for someone to write a power menu options and enable stock tethering script =P
Sent from my SAMSUNG-SGH-I747 using xda premium
You might try wiping data for gallery app and I think it's media storage app...see if that helps with gallery.
Toested said:
You didn't happen to play with the camera at all, did you?
I can live with the Fix Permissions via CMW, so that would clear up 2 out of 3 of my problems. All I need is a fix for the Gallery problem, and I can go back to Official JB.
Thanks!
Click to expand...
Click to collapse
Flashed this over stock and works flawless no lag no stutter. Thx
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ak907 said:
This is my first post, so it would not let me reply to the thread here
http://forum.xda-developers.com/showthread.php?t=1739426
i wanted to give thanks as i really appreciate the rooted stock ATT 4.1.1 ...... your super quick! I am up and running jelly bean now, and i still have my root... i had a minor issue of odin saying "pass" after flashing but my phone was stuck in boot loop untill i went into recovery mode and did a factory reset. Im not sure if that is normal or not but whatev it works great now
Click to expand...
Click to collapse
Wanted to say the same thing. ..thanks all came from black jelly to rooted jb with mobile Odin with no problems !
Sent from my SAMSUNG-SGH-I747 using xda premium
Anyone figure out how to enable stock jellybean lock screen?
Sent from my SAMSUNG-SGH-I747 using xda premium
Neflhiem said:
Wanted to say the same thing. ..thanks all came from black jelly to rooted jb with mobile Odin with no problems !
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I kinda miss the added features from the rom I was on frosty jb but I'm adding things here and there, wish we had multiview seems cool but I'm just waiting for the 4.2 roms to start coming out but so far not too bad, except the flash counter thing, but I'm happy with it so far just need someone to put out a hd theme like the one I had on my phone before but that to will come, also glad that the 4.2 camera with photosphere still works that feature is cool
Sent from my SAMSUNG-SGH-I747 using xda premium
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
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
It is a rooted samsung galaxy s4 M919 from t-mobile
is it stock rooted or what ROM are you running ?what kernel? what settings ? what mods? we need some detail sir but for starters if you can get it to boot try *#2263# and if its not set to automatic try clicking your options auto is the default setting
bobolinko said:
this morning I got unfourtunately, the process com.android.phone has stopped and cannot get the phone to boot without constantly hitting the "OK"
I see there is no signal, and can see in the phone information that the radio is turned off. I have an app that used to get to the screen but now it hangs due to the phone has stopped issue.
Is there any way I can turn the radio on by using some code with the dialer pad?
I have tried recovering 3 other nand backups, but none work. all have the same result.
Thanks for any help someone might be able to give me!
Remove your sd card sim card and battery let set 10 minutes put back in see if the message is still present if so you might need a new sim card.
Click to expand...
Click to collapse
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Might just be a lemon. I would just flash back to stock then take the phone and get a replacement.
bobolinko said:
I have tried both of the above suggestions and no joy!
I have 2 nandroid backups that were done when the phone was working fine, and recovering either one has the very same symptoms.
I'm not sure that all the phone is backed up or restored in entirety, unless there it a hardware fault in this phone. It's 31 days old today..... :<(
if anyone else has any ideas, I'm all ears!
Thanks!
Click to expand...
Click to collapse
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
tylerholbrook said:
You still have given us no details on what you are running, stock, rooted, touchwiz, aosp. Do you know how to Odin back to stock? Sounds to me what happens when you flash a modem not meant for the phone.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
bobolinko said:
OMG! Sorry! It is a STOCK ROOTED SGH919, 4.22 M919UVUAMDL W/ 3.4.0-453951 Kernel
Thanks!
Click to expand...
Click to collapse
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
tylerholbrook said:
Odin back to stock I would think should alleviate your problem. I flashed an international modem when I was running omega rom and got flash happy when I was drunk. Had the exact same problem you are describing odin to stock worked for me
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Glad I could help. The modem isn't in your back up that's why back ups won't fix this problem. As for apps, it's from syncing your Google account. Aloha
Sent from my SGH-M919 using xda app-developers app
bobolinko said:
Yo Tyler!
I was not drunk nor did I flash anything, it was going fine and suddenly, poof!,,,,,
Anyway, I tried your suggestion and IT WORKED! I also saw, (I don't know how/why) all my apps being installed automatically!
Well, almost all anyway. I had to install only maybe 3 apps, and that was all. Even my keyboard configuration that I made lots of cosmetic changes to- via the apps setup, was like I had set it up as... Weird, but great for me!
Thanks for your suggestion. It's quite odd, as one of the nandroid backups was made using the exact rom image that I used to Odin back to stock....
Nevertheless, as the Hawaiians say, MAHALO NUI LOA! Tyler No Ka OI (Tyler is the best)
Aloha...
Click to expand...
Click to collapse
If you chose to have Google back up and restore your apps, it will do just that.
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
I'm sure I'm not the first one and only one who got this message. Could anybody please help?
Thank you very much!
testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Irwenzhao said:
I don't know about stock, but flashing a custom ROM should fix it. (Try reflashing stock 4.1.2)
Smack that thanks button If I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
Click to expand...
Click to collapse
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
testrider said:
I don't know why flashing a custom ROM would fix it, as I did not have this before and I did not change
my ROM...
Click to expand...
Click to collapse
U could try reflashing stock rom if u don't want a custom one.
Smack that thanks button if I helped!
Note 2 LTE powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. replies with quotes will be replied to faster.
testrider said:
What caused this error message and how do I get rid of it? When I did something related to the settings, like turning on/off airplane mode, the error message "Unfortunately Settings has been stopped" popped up and I had to click OK for it to go away. However, it did not seem to affect anything else...
It also came up right after my Note 2 finished reboot.
Anybody knows why it happened? It just happened in the last couple of days and nothing was changed.
My Note 2 is running stock JB 4.1.2, rooted with CF Autoroot.
Thank you very much in advance.
Click to expand...
Click to collapse
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
0.o said:
I would just re-flash a stock rom. Maybe stock+root. Sorry I've rooted many times and never had that issue on a stock rom.
Click to expand...
Click to collapse
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
testrider said:
Thanks for the reply. It'll be great if I can find out why then I can fix the root cause. We really don't want every time we have a problem we just do factory reset/wipe all/reflash and pray for the best?
It really seemed that there was no answer. I googled it and saw lots of people having the same problem but no solution.
I may have to flash the stock rom but I don't think that will fix the problem. Mine is running a stock ROM
Click to expand...
Click to collapse
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
The only way to get to the root problem is run a logcat of the error. We could guess all day long. I mean did you freeze anything, delete anything, flash a mod, use an xposed module? There are hundreds of things that could be wrong, but without a logcat it would take a long time to guess your specific error.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
testrider said:
Thanks. I'll remember to get a logcat next time. Right after the message popped up, correct?
Click to expand...
Click to collapse
Yep right after it happens. If there is something that triggers it. Reboot, to clear the log, then trigger the fc and pull log
Sent from my SGH-T889 using xda app-developers app
I had my htc one replaced under warranty for battery issues and purple camera issue.
My new one is running latest nusense rom but i had the same issue on stock debloated/deodexed rom.
Sometimes the screen just won't turn on. It appears that issue is only present when charging. Last time it happened i was tethering and internet connection was fine even though the phone was unresponsive.
The only solution is reset by holding the power button.
Any ideas?
thatsonlyme said:
I had my htc one replaced under warranty for battery issues and purple camera issue.
My new one is running latest nusense rom but i had the same issue on stock debloated/deodexed rom.
Sometimes the screen just won't turn on. It appears that issue is only present when charging. Last time it happened i was tethering and internet connection was fine even though the phone was unresponsive.
The only solution is reset by holding the power button.
Any ideas?
Click to expand...
Click to collapse
Is the USB OEM, ive had cheap cables from china do this to me in the past.
I've tried both the original and a knock off cable but there is no difference. Today I realized that it happens even when the phone is not charging. So I guess I can rule out bad charging and cables.
I will try to keep it in the daydream mode today just to see if that makes any difference. I'm not having much hope though, I'll probably have to get another replacement.
thatsonlyme said:
I've tried both the original and a knock off cable but there is no difference. Today I realized that it happens even when the phone is not charging. So I guess I can rule out bad charging and cables.
I will try to keep it in the daydream mode today just to see if that makes any difference. I'm not having much hope though, I'll probably have to get another replacement.
Click to expand...
Click to collapse
sorry to hear that, are you getting replacement from VZW or HTC?
Verizon. I replaced my original phone through them, it was easy and free. It sucks that i will have to pay for the sunshine root again.
I might try flashing new firmware first just to see if that makes any difference but i'm afraid it's hardware issue
synisterwolf said:
Is the USB OEM, ive had cheap cables from china do this to me in the past.
Click to expand...
Click to collapse
thatsonlyme said:
I've tried both the original and a knock off cable but there is no difference. Today I realized that it happens even when the phone is not charging. So I guess I can rule out bad charging and cables.
I will try to keep it in the daydream mode today just to see if that makes any difference. I'm not having much hope though, I'll probably have to get another replacement.
Click to expand...
Click to collapse
I remember there was an issue like this with other older HTC models, like the Rezound... Try, if you can, upping the min frequency up one notch. Synisterwolf remembers this old issue.
That can be a temp fix until you get your replacement.
Sent from my HTC6500LVWBLU using XDA Free mobile app
thatsonlyme said:
Verizon. I replaced my original phone through them, it was easy and free. It sucks that i will have to pay for the sunshine root again.
I might try flashing new firmware first just to see if that makes any difference but i'm afraid it's hardware issue
Click to expand...
Click to collapse
i would take your Paypal statement and pm jcase and tell him whats going on. maybe he can work something out with you.
Ive had my share of lemons from VZW. i hope you have better luck with the next one.
So far daydream mode seems to be preventing screen from freezing. i will try upping the frequency.
is it possible that this is software issue if it works?
thanks for all your help, it's much appreciated!
Also does anyone know what stock default frequency is? I'm pretty sure that i selected default upon installation but i'm wondering if i might have accidentally underclocked. My default was 384, i upped it to 486.
I'm just hoping that this is just a kernel issue i guess lol
Even though i had it happen on stock deodexed rom too. I'm not sure about full stock because i rooted and flashed immediatelly lol
thatsonlyme said:
Also does anyone know what stock default frequency is? I'm pretty sure that i selected default upon installation but i'm wondering if i might have accidentally underclocked. My default was 384, i upped it to 486.
I'm just hoping that this is just a kernel issue i guess lol
Even though i had it happen on stock deodexed rom too. I'm not sure about full stock because i rooted and flashed immediatelly lol
Click to expand...
Click to collapse
When it does it freezing thing and you reboot into android pull a last kernel message like this ...
Code:
adb pull /proc/last_kmsg
Upload it as a .txt file to xda so we can take a look...
Thx Josh
Looks like frequency change did the trick. It's been working fine since i change it.
When I get a chance, I'll try to set it back to 384 and pull the kernel message. Thanks Josh.
lj50036 said:
When it does it freezing thing and you reboot into android pull a last kernel message like this ...
Code:
adb pull /proc/last_kmsg
Upload it as a .txt file to xda so we can take a look...
Thx Josh
Click to expand...
Click to collapse
is there any way i can pull last_kmsg without adb and save it on my phone, download it later? this damn thing just won't freeze now when I'm home and I won't have access to my computer with adb later so I wonder if I could just pull it through root explorer. I located the file but can't figure out how to open it from my phone.
thatsonlyme said:
is there any way i can pull last_kmsg without adb and save it on my phone, download it later? this damn thing just won't freeze now when I'm home and I won't have access to my computer with adb later so I wonder if I could just pull it through root explorer. I located the file but can't figure out how to open it from my phone.
Click to expand...
Click to collapse
Last_kmsg is the kernel log from last boot. Just go into any file explorer that has root permissions and go to /proc folder. Copy the last_kmsg file to your SD card
Sent from my HTC6500LVWBLU using XDA Free mobile app
I had the same issue with my lg g. I think its a kernel issue. Not sure about yours.
Uzephi said:
Last_kmsg is the kernel log from last boot. Just go into any file explorer that has root permissions and go to /proc folder. Copy the last_kmsg file to your SD card
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
I tried that yesterday but for some reason it wouldn't copy. I guess I'll just have to wait until it happens when I'm home.
mudassirrashid said:
I had the same issue with my lg g. I think its a kernel issue. Not sure about yours.
Click to expand...
Click to collapse
I kinda hope you're right because the phone works great when I upped the minimum frequency and I don't feel like dealing with another warranty replacement, returning this one to stock and rooting my new phone.
What worries me is that it first happened on santods stock deodexed rom with stock kernel, now it's happening with santods nusense six with kernel that came with that rom.
I'm thinking about returning it to full stock but I really need tethering to work. maybe I'll just try stock rooted with wifi tether.
thanks for all your help guys!
thatsonlyme said:
I tried that yesterday but for some reason it wouldn't copy. I guess I'll just have to wait until it happens when I'm home.
I kinda hope you're right because the phone works great when I upped the minimum frequency and I don't feel like dealing with another warranty replacement, returning this one to stock and rooting my new phone.
What worries me is that it first happened on santods stock deodexed rom with stock kernel, now it's happening with santods nusense six with kernel that came with that rom.
I'm thinking about returning it to full stock but I really need tethering to work. maybe I'll just try stock rooted with wifi tether.
thanks for all your help guys!
Click to expand...
Click to collapse
Welcome dear
So i tried new lunar kernel on default settings, it froze again 10 minutes after i left home. Once again i couldn't pull last_kmsg. At this point i'm pretty sure it's a hardware defect. I guess another trip to Verizon store is in order
Yesterday i returned the phone to stock, leaving it rooted and s-off. No freezing at all so far. So i guess it's not a hardware issue. I'll try installing older version of TWRP recovery and try to do fresh flash of nusense.
flashed back nusense with an older recovery with all stock settings last night, this morning the phone wouldn't wake up.
finally managed to pull last_kmsg. (i had to upload it as zip file, it wouldn't allow me to upload the file with no extension)
thatsonlyme said:
flashed back nusense with an older recovery with all stock settings last night, this morning the phone wouldn't wake up.
finally managed to pull last_kmsg. (i had to upload it as zip file, it wouldn't allow me to upload the file with no extension)
Click to expand...
Click to collapse
Cant unzip that zip file..... :fingers-crossed:
Thx Josh