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)
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
Hi everyone. It's been two days since the process com.google.process.gapps has started crashing, "stopping unexpectedly" whenever i use the browser on my tab.
Reading the error report, it seems (not 100% sure about that) this is somehow related to the bookmarks sync with Chrome, but i can't find a way to disable this.
Has anyone exprerienced the same issue? Any known solution? Thanks
Go to settings > accounts and sync, click on your account then uncheck everything, then manually sync everything one by one to see what is causing the error.
Then go to manage apps and clear the cache of all the problem apps and re-sync them once you're done. It might take a few tries but it should take care of that error.
I'll try that as soon as possible, thanks!
browser sync was causing this for me
I believe that bookmarks sync no long works with galaxy tab. Google changed something on their end that should have worked fine(it still works on the xoom, transformer, etc.) but since samsung changed a bunch of stuff for no apparent reason, it is now broken. samsung is so stupid sometimes..
So you're basically suggesting that bookmarks sync should stay off to avoid problems like that?
well I don't really know. I never used bookmark sync in the first place. I'm just going by what is said in this article.
http://www.zdnet.com/blog/perlow/br...gle-or-the-oems/17840?tag=mantle_skin;content
It turns out that at some point Google started making some changes to the backend systems that handle Google’s user account data. There’s nothing wrong with them doing this; it happens all the time. In fact, no other Android 3.1 tablets had any issues at all with the changes, and their bookmark sync continued to work without a blip on the radar.
Not Samsung, however... I did some digging around the internet, and it’s become somewhat well-known amongst Android developers that Samsung actually modifies core source code in the Android operating system that handles communicating with Google’s backend data services.
Click to expand...
Click to collapse
Well, that's a pity. I had just started to think it was a useful tool to keep track of unread web pages between work, home and outside...
Let's hope Samsung somehow fixes that.
PS: disabling bookmarks sync actually stops the process from crashing, I think I've solved (if we could really say so...) the issue. Thanks to all!
Thanks, disabling auto sync for browser has stopped the error. Samsung developers need to fix this - I can't auto sync my gmail
What am I missing here?
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Hello,
Based on your post, I would suggest that you search your phone's development forum on XDA for a compatable clockwork recovery mod which will install a custom recovery on your phone. The thread will give you instructions on how to do so and how to enter recovery mode.
You can then enter the 'Backup and Restore' part of the recovery and restore your backup manually without using ROM manager. If this doesn't work, I would suggest that you then download the ROM of your choice and install it from the clockwork recovery. Make sure you clear user data and wipe the cache before you install.
Any fix yet? This is really annoying me as I rely on my bookmarks tremendously.
try this:
Open stock browser and under settings choose clear cache and deletehistory
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
alljokingaside said:
ok, for some reason, thought build.prop q's were relevant to the kernel...
anyway, I edited build.prop in /system with RootExplorer's text editor. changed the value for wifi.supplicant_scan_interval from 30 to 120. no extra lines or spaces, etc- just changed the number, saved, then rebooted. it took an obscene amount of time to boot up and the device stopped going into deep sleep after a short while. I installed better battery stats to see what was wrong and the app indicated mmc_delayed_work under kernel or partial wakelocks (i forget which). I restored the original build.prop and the device worked like normal.
Is this a bug or is ICS/JB different enough from GB that you have to go through alternate means to change build.prop (eg flashing an update script from CWM, or something similar)?
I've tried this twice already and gotten similar results and the method by which I edited the build.prop was exactly the same as I used to edit it on GB without issue.
another thread I checked out in the S II dev thread indicated that this is possible- editing build.prop (wifi scan at least, on top of a few others parameters)- w/o issue, so....yeah.
Click to expand...
Click to collapse
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Mevordel said:
I have no idea why that would happen, but I guarantee you the interval is fine where it is. I've left my player on with wi-fi over a week.
Click to expand...
Click to collapse
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
alljokingaside said:
I'm recording atm but problem isn't replicating. go figure; well, if it does, I'll post a logcat. if not, good for me since I forget to turn the wifi off most of the time and especially in places with no open wifi. anyway, I was posting this in case someone else did come across a similar problem and had a solution since my searches led nowhere (searching for anything mmc_delayed_work related comes up with little useful info/apparently a lot of once-valid GB tweaks are "busted"/not in ICS code base)
whether or not the scan interval isn't exactly the point, why I'm pursuing it; it's the specific point atm, but the general point is device ownership- tailoring your device to your heart's desire; complete ownership. that's the premise behind this whole site as I'm sure everyone here is aware. if I did something to mess it up along the way, great. but if it is a bug or something with ICS code base, it's be nice to know. a lot of folk like messing with build.prop so it'd be nice to know what can or cannot be messed with.
atm, it does look like I messed something up when editing and saving- perhaps I added a space or line where it shouldn't've been- since the device is sleeping as it should, again, if I find something, I'll post the logcat.
thanks for the re:
Click to expand...
Click to collapse
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Mevordel said:
I understand.
Thinking about it, mmc_delayed_work seems like it's tryng to catch up the SDcard or something. Did you reboot cleanly? That may be the issue.
Click to expand...
Click to collapse
No clue. what do you mean by "reboot cleanly"? if by that you mean, did I reboot using the reboot option in the power menu, then yes. always.
After restoring a backup and re-editing build.prop, sleep worked like gamebusters. Except, bluetooth auto-toggled on ("bluetooth is turning on"). After rebooting, it was stuck on the boot animation screen for a few minutes. A reboot after that pretty much boot looped it. I restored my backup afterwards...
Looking in the logcat (after editing), I noticed a ton of errors and permission denials.... Since I don't have much expertise here, I can't say for sure that they're normal but they seem to be abnormal. Wayyy more than I remember seeing when I browsed through before on a "clean" boot. But again, with the lack of expertise (or any functional knowledge for that matter)
==
Now, after having restored the backup before making the edits and rebooting, it seems to be stuck in a bootloop....huh. ok, after rebooting it 2x, it finally seems to have booted up "normally." Both before restoring (w/ edits and BT error) and after restoring (w/o build.prop edits), it's taking a lot longer to boot up than it used to....guesstimating 3-4 minutes. When it boots up, I get/got: "process system isn't responding" (both before and after restores now) and something about alarm error.
I've attached logcats of both pre- and post-event, if you're curious. As to "solving" this,I'm just gonna re-flash the PA ROM and wipe caches to get rid of these problems. ergh. device meets my foot against the wall is next on the checklist.
thanks again. I'd like to say, Stay classy, San Diego, but we all know San Diego and its class
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'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.