i've recently been encountering random reboots on my Galaxy Note 3 (N9005), on stock 4.4.2 ROM.
The reboot occurs regardless of time, foreground/background running apps, battery level and anything else i can think of. for instance, it can just instantly hang+auto-reboot while i'm browsing facebook, surfing on chrome, switching tracks on poweramp, or even when the screen is off doing nothing (deep sleep)!
I've tried to uninstall some of the recent installed apps, but still unable to find any culprit. is there any way i can identify the culprit, without resorting to factory-reset for my device? i spent a lot of time doing the configuration for each app that i use, and wouldn't want to repeat the whole process..
Thanks in advance for your help!
could anyone help please?
Only way to know would be to get a logcat or last_kmesg. You might try something like this since it is so random:
https://play.google.com/store/apps/details?id=org.jtb.alogrec
es0tericcha0s said:
Only way to know would be to get a logcat or last_kmesg. You might try something like this since it is so random:
https://play.google.com/store/apps/details?id=org.jtb.alogrec
Click to expand...
Click to collapse
i downloaded aLogRec as requested and recorded the log for the entire day.
this is the log for the first 16hours - i opened it with notepad++ and the log was super short - is it normal?
Link 1
this is the log for the next few hours, where the random reboot occurred halfway - seems that it's empty. does that mean there's no way for me to know how the reboot came about?
Link 2
dylansmith said:
i downloaded aLogRec as requested and recorded the log for the entire day.
this is the log for the first 16hours - i opened it with notepad++ and the log was super short - is it normal?
Link 1
this is the log for the next few hours, where the random reboot occurred halfway - seems that it's empty. does that mean there's no way for me to know how the reboot came about?
Link 2
Click to expand...
Click to collapse
Yea, that app definitely didn't work. Not really sure why. But other than catching it in the act using the logcat, whether it is another automatic one or just the manual way via the phone or computer, there's no other way to tell. You do know that you can backup most of your apps and settings with a variety of tools? It won't make everything perfect, but cuts the time of restoring your phone after a factory reset way down. I literally wipe my entire phone and reset it up like 3 times a week on average. It usually takes me about 20 minutes to an hour depending on if I just need it usable or exactly the way I like it.
es0tericcha0s said:
Yea, that app definitely didn't work. Not really sure why. But other than catching it in the act using the logcat, whether it is another automatic one or just the manual way via the phone or computer, there's no other way to tell. You do know that you can backup most of your apps and settings with a variety of tools? It won't make everything perfect, but cuts the time of restoring your phone after a factory reset way down. I literally wipe my entire phone and reset it up like 3 times a week on average. It usually takes me about 20 minutes to an hour depending on if I just need it usable or exactly the way I like it.
Click to expand...
Click to collapse
thanks for the reply. got a few questions:
1. other than aLogCat, any other app i can try to catch the random reboot in the act?
2. yes, i could backup all my apps+settings using TB, but would i also be restoring the 'random reboot' in this case as well?
3. another symptom just occurred and i'm not sure whether it's relevant to the random reboot. after the random reboot (or so it seems), all my saved WIFI passwords get forgotten, and i need to re-enter the passwords for it to auto-login to my home/office network. i also realize it loses one of the settings i previously adjusted in Developer Options - the transition animation scale was set to 0x last time and set back to 1x.. but when it random reboots nowadays, it will just default back to 0x (which isn't the correct default).
i'm so frustrated at the number of problems my phone is facing right now..
dylansmith said:
thanks for the reply. got a few questions:
1. other than aLogCat, any other app i can try to catch the random reboot in the act?
2. yes, i could backup all my apps+settings using TB, but would i also be restoring the 'random reboot' in this case as well?
3. another symptom just occurred and i'm not sure whether it's relevant to the random reboot. after the random reboot (or so it seems), all my saved WIFI passwords get forgotten, and i need to re-enter the passwords for it to auto-login to my home/office network. i also realize it loses one of the settings i previously adjusted in Developer Options - the transition animation scale was set to 0x last time and set back to 1x.. but when it random reboots nowadays, it will just default back to 0x (which isn't the correct default).
i'm so frustrated at the number of problems my phone is facing right now..
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=scd.lcex - looks pretty solid and more updated than the other one.
Possibly, but since we don't know what caused it, no way to know. What you do is backup everything, reset, then test, then start to add apps back in and test. Sucks, but just one of those things. Software issues can be tricky because there are so many different factors in play.
But it seems like this might be an issue with certain Samsung phones with batteries that are not performing as they should:
http://forum.xda-developers.com/showthread.php?t=2567941&page=3
es0tericcha0s said:
https://play.google.com/store/apps/details?id=scd.lcex - looks pretty solid and more updated than the other one.
Possibly, but since we don't know what caused it, no way to know. What you do is backup everything, reset, then test, then start to add apps back in and test. Sucks, but just one of those things. Software issues can be tricky because there are so many different factors in play.
But it seems like this might be an issue with certain Samsung phones with batteries that are not performing as they should:
http://forum.xda-developers.com/showthread.php?t=2567941&page=3
Click to expand...
Click to collapse
alright, will try the Extreme version and hopefully it catches the culprit.
As for the battery problem, it doesn't seem like the same case as mentioned in the other thread - he had a reboot loop and crazy drain, both of which are not existent (luckily) symptoms on my end.
Your issues could definitely be explained by battery issues though. Have seen stuff like this before at my shop. Batteries are less than $10 typically and worst case, you have a spare battery so if you go out and about and the phone dies, you don't have to run to a charger / outlet.
es0tericcha0s said:
Your issues could definitely be explained by battery issues though. Have seen stuff like this before at my shop. Batteries are less than $10 typically and worst case, you have a spare battery so if you go out and about and the phone dies, you don't have to run to a charger / outlet.
Click to expand...
Click to collapse
hmm, pretty sure it's not a battery issue then. just bought a new battery and the same problem exists.
my logcat files appended as follows: https://www.dropbox.com/s/yjtio2je6h71mre/LogCat.zip
would appreciate everyone's help!
thanks!
I was experiencing random reboots on the stock ROM for my KFHD when I was running stock. Turns out it was caused by me adjusting the DPI to a custom value.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
I was experiencing random reboots on the stock ROM for my KFHD when I was running stock. Turns out it was caused by me adjusting the DPI to a custom value.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
that could be one possible cause as I have certain preset dpi's for apps using Xposed.
any other possibilities and any other way to avoid it?
dylansmith said:
that could be one possible cause as I have certain preset dpi's for apps using Xposed.
any other possibilities and any other way to avoid it?
Click to expand...
Click to collapse
The only thing I can suggest is resting the DPI to stock, unfortunetly. Or a DPI that is known to work well with your device.
Ph0enix_216 said:
The only thing I can suggest is resting the DPI to stock, unfortunetly. Or a DPI that is known to work well with your device.
Click to expand...
Click to collapse
just curious - did anyone look through my logcat to see if there are other causes? i already restored to default DPI but still experiencing the same issues.
Related
I just recently got the vibrant and got the OTA the same day, the gallery freezes about half the time, and about half of the time that it freezes i have to pull the battery, i cant get to task manager or put the phone to sleep and wake it up.
I searched google and there are alot of links regarding it but i didnt find any that gave any ideas to fix it.
I searched this forum and nothing came up. Anyway, I have a class 6 card, the gallery on my nexus is very quick and has never frozen, so it is definitely the phone.
In my experience with the g1, MT3g, N1 and now this vibrant, any time ive received an OTA it has come with costs, it always brings fixes and features but also causes new problems, large and small. So I dont doubt what I found while searching, that the gallery issue is a result of the recent OTA for the GPS fix. Anyway, its kind of silly that this awesome, technologically advanced device freezes when you open up one of the native apps. But can we do anything about it? And if not, is it likely that Samsung will address it in another OTA? thanks
edit: ive also just recently had my phone just turn off every day or so, and it wont power back on until i pull the battery. Maybe these 2 issues mean i have a defective device? Or is this par for the course with the tmobile galaxy s?
Overclock your phone to only run at 800-1000MHz. It completely solved this for me, 400-1000MHz still hiccups.
thank you, yet another reason to root i suppose...
So no way to fix that with stock phone? =(
heygrl said:
Overclock your phone to only run at 800-1000MHz. It completely solved this for me, 400-1000MHz still hiccups.
Click to expand...
Click to collapse
overclock huh,, i never tried i am there is a link here let me go look or how did u do it
/
That is odd, I've never had my gallery freeze or my phone reboot... Are you sure you don't have some rogue app? Perhaps you should factory reset and start fresh? Do you have any "junk" apps on your phone (stupid apps)?
I had a freeze on opening gallery right after the JI6 was released. I think it was trying to recreate the thumbnails from scratch and download pics from my Picasa acct.
Happened one time only and I actually had to pull the battery since it went unresponsive. Never had a problem after that.
~SB
perhaps unmount and remount the INTERNAL memory card. I've done this before just because I saw it as a suggestion and it recreated my gallery.
I having the same issue. I am ready to delete it and use a different app. Is that possible?
acjames said:
I having the same issue. I am ready to delete it and use a different app. Is that possible?
Click to expand...
Click to collapse
If you're rooted you can probably remove it.
I have tried factory reset so I don't think its a rogue app. I got the ota the day I got the phone so I can't compare before and after. If some people aren't having the issue period maybe a warranty replacement would resolve it. Of course, if we do end up getting froyo maybe that's something that will improve. Love the phone either way, I just get fed up with stuff like gallery freeze, random reboot, GPS issues, etc... stuff that i would think shouldn't get past product testing.
OP, this is discussed at the thread below. (use the search next time)
You are not the only one having this issue.
http://forum.xda-developers.com/showthread.php?t=805784
Quick Summary:
- Even with the removable card blank, the Gallery still have the same issues.
- I did a complete wipe and still have the same issues.
- I cleared data through System Settings which recreated thumbnails and other data, still have the same issues.
androidmonkey said:
OP, this is discussed at the thread below. (use the search next time)
You are not the only one having this issue.
http://forum.xda-developers.com/showthread.php?t=805784
Quick Summary:
- Even with the removable card blank, the Gallery still have the same issues.
- I did a complete wipe and still have the same issues.
- I cleared data through System Settings which recreated thumbnails and other data, still have the same issues.
Click to expand...
Click to collapse
Wow i am so sick of reading some loser tell somebody to "search next time". You'll be so very relieved to know that I actually did search, and all i found out is that you dont have any friends. But honestly I did find your thread, however it didnt seem to me to be on point with what i wanted to ask specifically. Your post says that "watchdog" told you your gallery is a "resource hog" and that you have to kill it. I dont know what watchdog is, nothing told me anything i just cant get into my gallery app very often, so that didnt seem applicable. Also, i got ji6 the day i got my phone so putting the gallery issue in the context you did ("since ji6 update") didnt mean anything to me, i dont anything about this phone pre-ji6 update. All I know is that my gallery app sucks, your thread was a bit technical for me to be able to apply to my particular issue
Anyway, now my gallery freezes every single time i initially try to open it, i have had to pull the battery 6 times in a row, it works after the pull. This has been my favorite android phone (of 4) but now i just want to set it on fire and run over it with my car. I guess Samsung and Android arent interested in making their $600 products work, does anybody know how i can fix my phone so that it does what it is supposed to? Also im not rooted which i assume probably makes it impossible for me to fix? thanks for any help.
DMaverick50 said:
Wow i am so sick of reading some loser tell somebody to "search next time". You'll be so very relieved to know that I actually did search, and all i found out is that you dont have any friends.
Click to expand...
Click to collapse
lol
also bump
Ok guys, I've read a lots of posts of people having sleep problems with frx07.
I installed it and I didn't had them...in the very first days...
After something has changed and my phone never went to sleep again.
I've read lots of post trying to fix it (hoping that someone already found what was keeping the phone awake) but I didn't found anything useful.
So I tried to solve it by myself and... i did it.
Using getlogs I tried to diagnose the problem but it contained nothing useful.
I killed every process, uninstalled from /system/app the apps I don't use (like chinese/japanese IME) and I left running only "really necessary" processes.
PS show only few (system's processes) but the phone didn't go to sleep aswell.
(I can upload the ps results if you need it)
Initially I thought it was something I installed (because the stock FRX07 didn't had the problem) so I made a complete backup (of the sleepless system) with titanium.
I removed the data.img and I started "from scratch" without replacing kernel/rootfs.
The phone could successfully sleep again.
I did a total restore from titanium and the sleep problem appeared again.
I deleted data.img again, letting the system to create again an empty one.
As I said before the default data (empty phone) works and the phone sleeps.
I thought "if an app I installed caused the problem let titanium restore system data only (without restoring any user app)"
I restored system data only and... SLEEP PROBLEMS APPEARED AGAIN.
It was not an app I installed!!! I deleted again data.img.
I restored only GREEN items in titanium (that means only user-changed data like messages, apn, contacts, accounts, wifi, calls and so on) AND my applications (and their data).
The phone can successfully sleep now.
So..if you have a sleep problem:
open sd card and move titanium apk from andboot/apps/other to andboot/apps (in this way you will have titanium installed by default when you delete data.img)
boot into sleepless FRX07.
open titanium backup and make a full backup.
reboot into winmo.
delete data.img
boot into android (you will have a "just installed system")
open titanium backup and restore "user apps+data" and the green system data.
reboot android.
you should not have sleep problems again.
Now... it should be useful to investigate further and find out what system app DATA is causing frx07 to stay awake (because the system app only without data actually work).
Let me know if this works for you
I'm not sure I can agree with you. I use TB to backup all the time, and use the batch features to backup every thing in addition to restoring everything... So I am questioning those results... I've never had issues with sleep - assuming I don't have GPS enabled or there's not some app screwing it up, honestly...
I'd have to say your experience was unique - unless someone else can reproduce these results, I'm going to say there's something else going on here...
this orange light is killing me too n i really dont knw wat to do....i have to quetion ur #8 step thou...how do i reboot to android? never heard of that
prexzone said:
this orange light is killing me too n i really dont knw wat to do....i have to quetion ur #8 step thou...how do i reboot to android? never heard of that
Click to expand...
Click to collapse
Ehh... shut off phone, boot WM, launch haret?
P.S: English is not my first language and I had trouble understanding parts of your post, hope that's what you asked.
prexzone said:
this orange light is killing me too n i really dont knw wat to do....i have to quetion ur #8 step thou...how do i reboot to android? never heard of that
Click to expand...
Click to collapse
I'm sure he means reboot the phone to WinMo, then hit HaRET to get back to Android.
You really should take a little more time compiling your posts. They are quite difficult to read at times... It would be appreciated, as others obviously have problems reading your posts as well...
arrrghhh said:
I'd have to say your experience was unique - unless someone else can reproduce these results, I'm going to say there's something else going on here...
Click to expand...
Click to collapse
+1.. Haven't experienced this issue.
Eodun said:
Ehh... shut off phone, boot WM, launch haret?
Click to expand...
Click to collapse
Yes. Did someone with the sleep problem tried my steps? Did you solve the problem?
arrrghhh said:
I'm not sure I can agree with you. I use TB to backup all the time, and use the batch features to backup every thing in addition to restoring everything... So I am questioning those results... I've never had issues with sleep - assuming I don't have GPS enabled or there's not some app screwing it up, honestly
Click to expand...
Click to collapse
If you don't have the problem then you don't need the solution and you don't have the possibility to agree. I have titanium backup too with scheduled backups. The problem is not in tb, I never said it, it's in FRX07 actually. I'm saying that there's something in frx07 that causes the phone to stay awake. (And trying step by step I found the problem to be related to some system app data).
You could say "you messed up your install" (I thought it too!!) but this "phone not sleeping" seems to be a common problem (so maybe I messed up but more likely there's something that's not working as expected and on some models or after some user operations the system "hangs")
So... If you have (or will have) sleep problems then you can try to do the steps I suggested to fix it. In my case it worked and it solved my problem it could be worth to try, no?
BTW: even the clockworkmod recovery restore problem seemed to be only mine.. lots of people said "it always worked, I'm using it since I was a baby".. but on some special conditions the bug was replicable and I fixed it.
http://forum.xda-developers.com/showthread.php?t=1154892
http://review.cyanogenmod.com/#change,6872
LinoX said:
You could say "you messed up your install" (I thought it too!!) but this "phone not sleeping" seems to be a common problem (so maybe I messed up but more likely there's something that's not working as expected and on some models or after some user operations the system "hangs")
So... If you have (or will have) sleep problems then you can try to do the steps I suggested to fix it. In my case it worked and it solved my problem it could be worth to try, no?
Click to expand...
Click to collapse
Ok, so you messed up your install. Happy? .
I'm honestly not sure. Until it can be recreated, I'm going to have to err on the side of user err .
I'm honestly glad that you resolved the sleep issues on your device. I just don't think it's a very good assessment of the sleep issues (you never really seemed to pinpoint it?) and I don't think it's a very good solution for newbies to try. Perhaps if they've exhausted all other avenues and your solution works - then we do have a bug. But now let's try to track it down... where is this happening? Why is this happening? I have a feeling that something you have done has caused this, but there's no way I can be for sure... other than not many people have persistent sleep issues. If they do, it's pretty much always been an app/widget assuming they follow the rules on GPS .
One thing I just found: com.android.email has a MAJOR cpu hogging bug. If you have an exchange account set up and have it polling instead of push or manual, AND you have a situation where data is unavailable, it goes into this braindead malloc/free cycle that eats up CPU like no tomorrow. If you google com.android.email cpu, this is a known issue that has been unfixed forever.
Not sure how many of those having sleep issues have this setup, but I recommend anyone using email to access an Exchange server to set it to manual or push. You can check this bug by running top, and cross-check via logcat -v time where the pid for email is doing a malloc spam.
-- Starfox
That was not my situation. Before wiping the phone I disabled the automatic data-sync (sync on background) and I didn't have an exchange account set up. (but i's nice to know about this bug maybe someone could benefit from your hint)
I know there has been a few threads about this but I kind of know the reason to my problem but I'd like it resolved.
It's caused by an application from the GO Launcher EX people, Go Battery & Power Widget.
So, I know this is APP specific but I'm figuring that it's also phone specific as I don't see anyone else having this problem in specific with it in the past few months or updates. Last was march.
It worked just fine up until yesterday when it started freezing the phone with the screen on and the plastic LED thing underneath the menu buttons on my Xperia U, if it doesn't freeze it randomly reboots whenever it feels like it and I'm quite positive this will in the long run harm my battery, I might just be paranoid but I think that it has affected or overloaded a few of the LEDs inside of the screen I can now find 3 dead pixels, I know that ain't much but it's kind of annoying as you may guess.
So, anyone know what I could do to solve this issue without removing the program or if it's a compatibility issue with something else, any help at all would be swell - I would remove it if it were not for the fact that when it did work that it saved my battery quite dramatically.
Thanks in advance and thanks for reading my wall of text.
-
I just recently re-flashed my phone due to an annoying "update available" issue that wasn't removable, forcing me to create a backup, which I just now restored into the phone (It doesn't appear to be there now but the issue persist so now I'm confused as to what might be causing it)
Once again, I'd really like this resolved rather than factory reseting the phone and then start to re-fill it again.
Not quite counting the freezes and reboots, but it's well over 50 just today.
Hmm as u said that the problem existed even without go launcher so try logging when the screen freezes... We might see the problem there... Anyways I know you said you don't want to factory reset and stuff... But 50 above is harmful so I think flashing stock is a good idea
Cheers,
AJ
Have you tried removing the app itself to see that it stops freezes?
If so, then it is clear the app causes the problems. Then you should contact the developers of it, they shall have an email on google play.
If not, then I suggest you to go for a logcat and try to figure out what is the cause Sounds really weird and a stock reflash (without restore) seems to be the solution for me
Abhinav2 said:
Hmm as u said that the problem existed even without go launcher so try logging when the screen freezes... We might see the problem there... Anyways I know you said you don't want to factory reset and stuff... But 50 above is harmful so I think flashing stock is a good idea
Cheers,
AJ
Click to expand...
Click to collapse
I decided to re-flash it, went well and it's feeling healthier.
The problem was Xprivacy.
nintendojet said:
Have you tried removing the app itself to see that it stops freezes?
If so, then it is clear the app causes the problems. Then you should contact the developers of it, they shall have an email on google play.
If not, then I suggest you to go for a logcat and try to figure out what is the cause Sounds really weird and a stock reflash (without restore) seems to be the solution for me
Click to expand...
Click to collapse
I had some freezing issues even without it, but I mucked about and re-flashed and now it feels better, but I'm still sure it was Xprivacy. Don't know why though.
I have been experiencing a series of force closes. I am posting this to see if anyone else has experienced this, and whether anyone can suggest a fix. I'm pretty sure it was something I did, but I'm not sure what. I'm hoping that this can maybe narrow it down.
Device: SM-N900P
Firmware: OC5, stock, rooted, with several tweaks and modifications(detailed below).
The problem: I am getting several force closes. They only occur when I am trying to open certain settings. So, they aren't just popping up at random. They are slightly troubling, but not really problematic. Which is to say, aside from the actual force closes themselves, I don't really seem to be experiencing any major problems. Here are the FC's I am experiencing:
-Menu> Settings> General> Battery: This one results in a "Unfortunately, Settings has stopped" dialog box, and an immediate return to my home screen. So, I can't check out my battery usage. I'm not seeing any crazy battery drain. By opening Root Explorer and navigating to data> system> batterystats.bin, and deleting batterystats.bin, the problem is kind of fixed- I can open battery from the settings menu after that. But there is only battery level and state displayed, no usage information(just a message saying it is not available).
-Menu> Settings> General> Developer options> Process Stats: Results in the same dialog box, and the background turns black if I don't press "OK". I'm not even sure what this does, but after my Battery started force closing, I started checking the rest of the settings out.
-Menu> Settings> Connections> Data usage: Dialog box, immediate return to home screen.
The probable cause: hard to say, I've done a few things to it. Like I said, I was hoping that someone would be able to figure out what I've done from the following information about what I have done so far. So, here goes.
I was on NK4, running Priest Punch ROM. I reverted to stock and took the OTA about a week or so ago. I immediately rooted and installed TWRP using the method in this thread: http://forum.xda-developers.com/note-3-sprint/general/how-to-root-note-3-lollipop-t3089382 .
After rooting, I didn't see a whole lot of OC5 development, so I started poking around to see what kinds of mods I could use. First thing I wanted to do was remove bloat. I started off using Root Explorer, then I happened upon this thread featuring a bloatware removal tool for the T-Mobile variant: http://forum.xda-developers.com/note-3-tmobile/development/tool-utility-sgn3-sm-n900x-bloat-t2813036 . It worked. I removed a bunch of apps, but nothing I wasn't sure I could safely remove(I had to check Google a few times). I did not notice any problems at this time.
Then I installed this mod to pump sound out of both speakers: http://forum.xda-developers.com/note-3-sprint/development/mod-sm-n900p-surround-sound-t2966042 . I did not notice any problems at this time.
Next, I decided I wanted more fonts, so uninstalled the preloaded fonts and pushed the apk from this thread: http://forum.xda-developers.com/showthread.php?t=2752379 . Again, no problems.
I decided that a working hotspot would be nice, so I used the method in this thread to get one: http://forum.xda-developers.com/note-4-sprint/general/lollipop-hotspot-root-flashing-t3048163 . I tested it and it worked. No problems.
I really wanted to silence my shutter sound, and I happened upon this Galaxy S4 thread: http://forum.xda-developers.com/showthread.php?t=2261789 . It worked, and there were no issues. This was my first exposure to csc codes. I found a similar thread for the s6( http://forum.xda-developers.com/galaxy-s6-edge/general/quick-guide-enabling-hidden-features-t3087506 ), and followed the instructions. I was able to enable the camera during calls and enable call recording. No problems here. I tried a keyboard mod from the same thread, which had no effect at all(good or bad), so I reverted the code for that one back.
This is when I think I started to go off the rails a bit. I saw a thread for the Polish variant of the Note 3, N9005. http://forum.xda-developers.com/gal...camera-mod-note-3-n9005-lollipop-5-0-t3067827 -it had a neat sounding mod designed to improve camera quality, remove recording time and snapshot restrictions, and make 60fps HD the default camcorder mode. It took a little trial and error to get it installed, but I was making backups of files I was messing with, and was able to quickly and easily reverse any missteps. Again, the mod works fine, and I have noticed no issues. So, I started looking at the dev's other work. Which led me to this thread: http://forum.xda-developers.com/galaxy-note-3/themes-apps/secsettings-mod-17-swipe-charging-t3046032 . I wanted some different unlock effects, and I wasn't really finding them, so I tried his mod out. It was a 3 step process: replace a SecSettings app, copy paste some .ogg files, and finally, copy paste a SustemUI .apk. The first two steps went fine, but the third resulted in a persisitent, repetitive dialog box. I forget what this dialog box said, but it popped up almost as soon as I could press "OK", and I had to restore the backup of SystemUI to make it usable again. Oddly enough, about half of the new unlock animations still worked fine, and I wasn't seeing any problems after that, so I left everything else there. I liked the unlock animations, and they didn't seem to be causing any problems after I restored the original systemUi .apk.
Let's see, what else might be relevant? I was using the built-in task killer quite a bit. I'm also using SetCPU. I have 2 profiles: Screen on, 1728 MHz max, 300 MHz min, governor ondemand. And Screen off, 1036 MHz max, 300 MHz min, governor interactive. And I have installed the Material Power Menu from this thread: http://forum.xda-developers.com/android/apps-games/app-materialpowermenu-reveal-animations-t3059169 .
I started to notice the battery FC last bight. So, I wiped the battery stats as outlined above. Noticed it again today, wiped stats again, and kept checking it. After about an hour, it was force closing again. That's when I started poking around and found the others.
I dunno if anything can be done about this, or if anyone might know what's wrong. And, like I said, Aside from these FC's I'm not experiencing any real problems. I'm a little worried that they may get worse, or turn into something more serious, but I can always restore a backup if that happens. But if there is some kind of fix for these issues, I would use it. Thanks in advance to anyone who takes the time to read this wall of text, and tale of irresponsible phonery.
These are all settings that monitor usage.... should that tell me anything? I have tried wiping cache and dalvik, but that only seems to fix battery usage and data usage very temporarily(like, for a minute or less). And it doesn't seem to have effect on Process Stats.
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
My thoughts:
Seeing as you have flashed a lot of mods, it could be anything. If it were me, I'd start the rom from scratch. Then for the first step, instead of removing apps, I'd freeze them with titanium backup and give that a day or two to check the stability.
If that works, I'd continue with the mods one by one, giving a day or so for stability checks.
If you'd rather not do all that, you could use a logcat to find the origin of the problems.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
GAPO said:
I'd probably try the logcat first. One, because I hate doing stuff over, and two, Ive neber done it before and it should be a learning experience. Is it complicated? I'm assuming there is a thread here on xda about it...
Click to expand...
Click to collapse
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
jlechner said:
It's fairly straight forward. I did one to see why an app wasn't loading, didn't need instructions. But that was a fairly simple check, yours sounds more complicated. I'd do a bit of reading on it.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Will do. Thanks for your help!
Okay well I decided to re flash OC5 and start from scratch.
I took it back to stock and re rooted. Am now debloating....no isssues yet.
I have flashed everything except the Polish camera mod and the wallpapers. Having zero issues of any kind. I know it can take difficulties some time to manifest themselves, but I'm betting it is either the lock screen animations or the camera mod. Leaning towards the lock screen animations because it involves messing with system.ui...
Okay, made a new backup and flashed the camera mod. No issues. After every mod, I have been going back and checking for issues. This is all stil pretty new, but if everything is still fine after a couple of days, well, I will be convinced that it was the lock rings. Not surprising obviously that flashing stuff meant for foreign variants can wreck your sh*t, lol.
Anyone else pixels getting very warm when just basic using the phone ? No gaming , no camera.
I'm using WiFi and just checking fb , chrome etc.
Phone is constantly warm
Not here. Constant warmth is a sign that something is using processing power all the time. Usually this is a app that has gotten messed up. You can try uninstalling and reinstalling all your apps, or do a factory reset/wipe. The factory reset/wipe is more likely to fix the problem, but it will also delete all of your apps and data (text history, etc) so make sure you backup anything you want to restore.
Running in safe mode is good way to test the rogue app theory.
If you just received the P6. Give it a few days.
When I first started using my P6. It was extremely hot for about two days. It was so hot that it scared me into thinking it was going to be toast soon.
But for some reason it went away.
There were quite a few other people back in October that also had the same issue when it was new.
Try a search in the P6 threads to read about it.
No such issue, even on first day of usage. Only warm came from 4K video on 60 fps for 10 minutes. But there's already a topic for this problem.
sic0048 said:
Not here. Constant warmth is a sign that something is using processing power all the time. Usually this is a app that has gotten messed up. You can try uninstalling and reinstalling all your apps, or do a factory reset/wipe. The factory reset/wipe is more likely to fix the problem, but it will also delete all of your apps and data (text history, etc) so make sure you backup anything you want to restore.
Click to expand...
Click to collapse
Too many apps to do that! I'll try safe mode
I don't have such problems on mine. Usually it is misbehaving app causing this. You can check battery stats in settings and see if there is app using too much battery to identify the problem.
Has anyone tried this Suduko game which works well on my Pixel 3.
But it now makes Pixel 6 very hot.
Any suggestions would be appreciated
Sudoku: Number Match Game - Apps on Google Play
Play Sudoku by Brainium! Solve daily puzzles, train your brain, and stay sharp!
play.google.com