I cannot find out whats going on with my phone. Ive tried 3 different roms, kernals, radios and settings and I cannot find whats going on with the phone. It locks up for the weirdest reasons at the weirdest time. I cant track down whats causing it, and it is completely random.
Heres a log cat Ive got from BAMF 3.0 RC1 stock kernal MR2
http://www.mediafire.com/?uxljp5prhzff8f7
and another
http://www.mediafire.com/?b9oc6x78ujk7axu
Please help... any ideas will help me out
BTW ive also tried all different kernal speeds and governers
Anytime i connect to usb for logcat it locks right away, and when I pull a logcat on the phone through a terminal emulator i get a the normal thread, but then one always pops up...
E/IPCThreadState (random numbers) failed to find cpu subsys
... any ideas?
http://pastebin.com/CLvMv5HC
^ During this logcat
First boot, fresh install of the new BAMF build 3.0 RC1. Phone is still running and responsive at this point. Ill try and get another when it locks
Didn't look as I can't on my phone but are you undervolting?
Sent from my ThunderBolt using XDA Premium App
joshnichols189 said:
Didn't look as I can't on my phone but are you undervolting?
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
Im running the kernals supplied and without editing them it will still do it
Can you please re-up your logcat dumps and put them on something a bit more friendly like pastebin.com?
Also, what exactly are you doing when you dumped these logcats (both in the foreground and background), just to get an idea of what was going on your phone at the time.
Were these lockups happening on froyo as well?
yareally said:
Can you please re-up your logcat dumps and put them on something a bit more friendly like pastebin.com?
Also, what exactly are you doing when you dumped these logcats (both in the foreground and background), just to get an idea of what was going on your phone at the time.
Were these lockups happening on froyo as well?
Click to expand...
Click to collapse
Ill link them now in the OP
altimax98 said:
Ill link them now in the OP
Click to expand...
Click to collapse
as far as what i was doing..... nothing most of the time lol. most of the time it would lock on connecting to a PC, other times it wont wake up, then some of the times it will lock in the middle of scrolling through tapatalk or browser. its completely random and i can track it down
See if you can find out what process that is (2660) or whatever happens to be in the current error message. Process ID will probably change over time, but it's linked to some process on the phone.
You can find out about the current processes by typing:
Code:
ps
in the terminal emulator
EDIT: Just randrom things that might be causing problems, but cant say for sure:
The error you're getting I think happens when a process is in sync with another end and something more or less hangs up on it or goes out of sync so it can no longer find it. Pretty sure it's related to the davlik vm. If so, try going into recovery and clearing your normal cache and your dalvik vm cache under advanced. If that doesn't work...see below:
1) did you restore any data from previous roms/builds for this? Either previous GB ones or from froyo?
2) since it happens when connecting to the pc, it could be the htc hub crap that's causing the problem. If so, i would try disabling or removing the app, it's not that needed.
3) Are you using setcpu? It might be interfering with things.
Did you wipe data and cache prior to flashing? I've found a lot of my issues are corrected by wiping app data with Titanium b/u.
Well guys thanks for all the assistance. Ive tracked it down to being the speedtweak.sh script. Something just never quite worked right and whenever i would set the speed, governer or attempt a tweek it would then start the errors.
On the new 3.0 Build with the toolkit i dont need to manually go into the script and it seems to work fine. it may have been user error, or something just didnt jive with the phone...
although i still get the same cpu subsys error, but no locks so far
Related
I am rooted and using the aloysius rom. I've been having trouble after the first time I downloaded something from the market...it just keeps hanging and not starting the download. Tried restarts and battery pulls, with no luck. Then I noticed a force close message for com.google.process.gapps. Searching around the net I found others with similar problems on other android phones, but had no luck there either. Their fix was to clear the cache for Gmail and Gmail storage, but this didn't work for me. Any ideas?
I had this issue, just wipe all your data and it should work.i know it's a hassle but it was the only way to get market to work again for me.
-------------------------------------
Sent via the XDA Tapatalk App
es0tericcha0s said:
I am rooted and using the aloysius rom. I've been having trouble after the first time I downloaded something from the market...it just keeps hanging and not starting the download. Tried restarts and battery pulls, with no luck. Then I noticed a force close message for com.google.process.gapps. Searching around the net I found others with similar problems on other android phones, but had no luck there either. Their fix was to clear the cache for Gmail and Gmail storage, but this didn't work for me. Any ideas?
Click to expand...
Click to collapse
Are you or have you recently started running a2sd? If so it sometimes breaks market. All you have to do (if you are running a2sd) is go to your adb command prompt and enter.
adb shell
cd system
cd bin
a2sd fixmarket
and just to be safe
a2sd clearcache or a2sd resetcache, then you should automagically reboot and the market issue should be resolved.
I tried the clearing the data thing and didn't make a difference, but yes, it probably had something to do with a2sd. I ended up switching to Legendary Kaos v17 since I just rooted the other day and am still having fun trying some different roms. This one seems to have all the stuff I need, so will probably stick with this one for a bit. Thanks for the advice though, it's still possible I might go back to it...
So, it happened with this one too. It must have something to do with some .apks I was deleting. I hate having all of these extra apps that I don't want, so was systematically deleting obvious stuff that wasn't useful like Twitter and the like. I'm not sure exactly which one causes this problem, but thinking maybe the browser... I got rid of it so I would only have one internet connection through Dolphin. Hmm...
I've tried everything I can think of or find in this subject but I can't figure it out.
I'm getting FCs all over and seemingly randomly.
There's no one program doing it either.
I've used cyanogen 7 7/17 version with glitch kernel (both 11 and 12) and the v3 kernel. Maybe the stock but I don't remember.
Also flashed the dl09 or which ever radio was recommended for cm7 on the ROM list sticky.
Tried the nighties and am on not the recent one but the one right before it with stock and glitch 11 and 12. Also tried before and after v6 super charger which seemed to make my launcher before faster and without the stopped responding dialog.
I also use the ultimate kernel removing script between kernels.
Here's what I've already done to try to fix it:
Wipe big 3. fives it for awhile then starts up in force.
Wiped to stock 2 or 3 times. Still happens.
Fixed permissions. Works longest so far but still starts up again later.
Wipe cache and data in manage applications settings menu for creasing programs. Works for a while usually but then goes
back to crashing.
I followed ask instructions to install everything properly.
The only thing is that
do I need a special bootloader with nighties and stock kernel?
What am I missing here? It seems like it's related to wifi because I can keep things stable a little longer with wifi off but it is not always 100%. Definitely related to internet. Also seems like the cache reaches 2-3 megs when programs crash
browser seems to be more likely to crash. Will crash constantly and I'll open up Firefox or opera wends everything is peachy. I think neither ox those browsers crash from what I can tell.
Oh and could it be gapps somehow. I'm not sure but it might be a case built that all the crashing programs are gapps.
I've tried the new version 2.2.5 I think posted somewhere and the original 2.2.3 I think. I'm pretty sure they both crash.
I'm maybe to frustrated to see what's right in front of me and I maybe have forgotten an important detail so please forgive and I'll be happy to provide any info.
This is near perfect and that's the thing that's holding me back right now.
Anyone else have this happen to them? Any advise?
Sent from my SCH-I500 using xda premium
How did you originally come to cm7..ie. What was your previous rom and kernel prior to making the switch?
What steps did you take to get to
mtd format?
And lastly I read your whole OP but am still unsure if you've tried Odin'ing a stock VZW official rom to start from scratch? (ie. Eb01,dl09, or ed05)
Edit: Also did you restore any apps or system data via titanium backup?
Sent from my SCH-I500 using XDA App
I've come to cm7 at least twice from a stock froyo ROM. I followed the directions in the sticky exactly. At least twice.
I did restore titanium but not from non-mtd. I reinstalled every app one by one after upgrading.
I'm thinking it might be the wrong gapps. If browser is a part of gapps, I'd betting on it then. It seems the fc's might all be related to
the various gapps.
That's the only thing that I can think if that I haven't tried.
Sent from my SCH-I500 using xda premium
Here's the latest gapps.zip includes market...don't know if you've tried this oneand I don't think it contains anything for the browser, but i'm not sure...its for Mtd builds.
http://forum.xda-developers.com/showthread.php?t=1191063
Edit: i'm also assuming you've ran fix permissions via cwm or terminal emulator right?
Sent from my SCH-I500 using XDA App
I'm making you assume a lot, sorry. Yeah. Did all that.
I'm trying to isolate it. I'm seeing that the force closings are maybe not so random.
It's the browser, google services framework and programs that I guess rely on browser. They are programs that access the http protocol. Reddit/f5, Chan browser etc. I've yet to have a program crash that was not accessing the internet like chuzzle.
Gmail does sometimes too.
Anyway, if they fc I go into manage applications and usually clear cache for the offending program Anne it works again until the cache gets up around 2 or 3 megs give or take.
I know people have been complaining about the data cutting in and out on this ROM so maybe that's involved.
I originally thought it was wifi because it seemed to only happen on wifi but i'm getting it on 3g but not as often.
I'm thinking that the data appears to be on but isn't and it's confusing programs but then there would be others with the problem. The other theory is that my cache space is fried.
Sent from my SCH-I500 using xda premium
In case someone finds this buried down here with the same issue, here's how I think I fixed it.
Wipe data again. Make sure you let the gapp installer install everything itself.
Titanium backup: restore missing apps (double check for went google apps) and data. Or hand install your apps and restore data.
I have the install location set to original.
That seemed to work even with the seeming wifi cut out and the whole thing.
I also didn't install Firefox or opera this time. That shouldn't be the problem but i'm recording it here anyway just in case.
Good luck
Sent from my SCH-I500 using xda premium
Hey guys. as many of you know i am no stranger to the Android system, although i have been pretty much totally absent from the forums since i got a job with limited privelages on my comp.
Before I explain what happened to me, i should say that i have not made ANY changes to my system for at least 4 months, with the exception of build.prop updates, which i my phone has been running fine on for weeks. i found a setup i liked and ive been running it, along with the same root applications, for quite some time.
With that said, heres my timeline of events:
Normal day, doing what i always do on my phone everyday: phone was plugged in to a wall outlet at my desk. streaming music, browsing web, youtube, etc. nothing out of the ordinary
i first noticed something wierd was up when i went to install an old .apk i had saved on my sd card. i opened it through file manager which, naturally, brought up the stock package installer. i clicked ok to install, and it said "installing"..however it nevver finished. it was stuck on "installing" for several minutes. i tried a couple more times, same thing kept happening. i had no idea what was going on.
i went into settings>applications>manage applications. i scrolled down to package installer and clicked on it, with the intention of clearing cache/data, however the values never loaded, it just kept saying "computing". it was doing that for all other apps i checked as well.
then i opened titanium backup and wiped data for package installer through that. operation was performed successfully.
i went to reboot my phone, and thats the last thing it remembers. now whenever i try to turn my phone on, it gets past the kernel splash screen and its all black from there (i have the "no boot anamiation" command in my build.prop). the only response i get at that point is the led buttons will light up if i tap them. i have to pull the battery to turn the phone off/reboot.
i tried pushing packageinstaller.apk to /system/app using adb but that didnt solved anything. i also tried wiping cache/dalvik and fixing permissions through clockwork. nothing has worked.
i am running Froyo Trigger w/ Bali kernel.
sorry for the long post, but i figured id be as detailed as possible to minimize questions.
any suggestions would be great. i ask that no one please suggest factory reset/reflash/odin. i realize that those options are there, but i consider them last resorts. id rather brainstorm a solution than bail immediately.
thanks ahead.
also i forgot to mention, there was nothing wrong with the .apk i was originally trying to install. i have installed it/uninstalled it many times. i tested other .apk files i had, but package installer still behaved the same way
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Br1cK'd said:
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Click to expand...
Click to collapse
not sure if i should be embarrassed to admit this, but ive never used logcat...ill look into that
Your first step there is to get the android sdk setup on your pc, then once adb is part of your command line the simple command is "adb logcat" without it quotes. That will start the log displaying in the command line window.
There are other options with the logcat command, that output the log to a text document and its more in depth, but I dont remember it off the top of my head. Maybe someone can post it for you.
The only caveat is how far your phone is booting before it hangs, I think logcat will show something, but won't know for sure until you try it.
Sent from my ZenDroid, meditating on the XDA App
http://forum.xda-developers.com/showthread.php?t=1319802
Eugenes Froyo that doesn't brick, followed by an Odin to jfd.
Sent from my SGH-T959V using XDA App
Okay so I took the plunge and installed my first ROM (ICS Collective Base4) among other things with my SGH-I717M (Bell). Everything went very well and here are the issues that despite reading over 500 pages in threads related to these issues, I have not been able to solve them (workarounds, sure). I'm hoping that others can confirm these glitches and whether or not they have been able to remedy them:
-Upon boot, "Unfortunately, the process com.android.phone has stopped". Annoying, but doesn't seem to affect anything. No workaround or solution.
-Baseband "unknown". Tried ODIN flash install AND coming from completely stock phone via CWM flash, neither has remedied this problem. Doesn't seem to affect anything so don't really care.
-Stock calendar application missing - really don't like some of the other calendars, but I can't seem to find the APK file in any other ICS ROM's out there, so I gave up on this. So workaround, no solution.
-Time zone wrong. Workaround is to deselect automatic network management and select the correct timezone. Reverts back to incorrect upon rebooting so apparently only a workaround and no solution.
-Upon booting setCPU max/min speeds are incorrect and you have to open the application for it to correct the speeds. Perhaps it's just the widget that's broken, but for now it's a workaround and I can't seem to figure out a solution. Quandrant benchmarks seem to indicate that if I don't do this, the performance is affected as if the speeds are 1242max/384min and not 1512max/384min.
-Phone freezes on "Power Off", have to hold power button - camera flash goes off and then restarts. Workaround seems to be to use terminal emulator or other applications to reboot, etc. Don't know if there's a solution to this.
-Wallpaper incorrectly zooms - workaround: market applications. No solution that I can find yet.
-Unrelated to the ROM, but V6 Supercharger - I can only get it to report 50% supercharged, even after modifying my services.jar file and following all "step 8" instructions (that was an undertaking!!!). Don't know what's up there, but maybe some of you super-techs have figured it out.
-Only 624MB of RAM available instead of 700MB+ with GB. Haven't heard anything about why this is, so no solution or workaround.
-Doesn't seem to be an ICS keyboard available? I think this can just be installed from the market but I haven't tried it so not sure.
I'm sure there's other things like with Swype, tethering, etc.. etc... that are not working but this is just what I've noticed within the last 8 hours of flashing and trying to set-up and configure. Any comments or helpful suggestions for a n00b like me?
Thank you for any and all feedback. Thank you to all the developers working hard on this fresh release to bring us a solid ROM!
Calender: http://dl.dropbox.com/u/569065/Calendar.apk
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
Remember, this is a leaked firmware, these bugs are within that leak itself and a few of these issues have been addressed (unknown baseband, etc..) And will be fixed when we release the actual full ROM. this is just the base we shared in the mean time. A few are still present likesome settings not sticking through boot, and the power menu hanging.
Click to expand...
Click to collapse
Absolutely. And considering what I've read about previously leaked versions of Android over the years, this one performs like a champ. Can't wait to see what comes out next, but I figured from what I've read this one works well enough to go the distance and install. Thanks again collective!
Felinos11 said:
Ithink is ur phone acting weird. Only the setcpu speeds not sticking and issue about wallpaper which can easily be fixed by using quicpics are the two issues my phone had. Just dnt use any cpu controller i noticed phone goes to sleep when no cpu controller while when there is cpu controller screen off speed sticks to 384 or 192
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yeah, just thought I would put my experience out there if it helps anyone or if someone could help me lol. It's very likely some of these are isolated problems, but most of them are problems with the leaked version. I uninstalled setCPU because I think you're right, something likes to nom nom the battery when the screen is off.
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
This is probably not the best Rom to run for your first flash. I would try one of the official releases in the development thread, unless you are an official tester for The Collective...
Can't wait till they release an official ROM ...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
mk2 love i see im a vr lover Mr helios
Sent from my SAMSUNG-SGH-I717 using XDA
Helios909 said:
Oh and here's something odd which I don't know if anyone else has experienced with ICS or GB, but Terminal Emulator doesn't allow me to type anything unless I capitalize each individual letter. Which of course is useless because it can't accept commands in caps. When I press any key in lowercase it's like I haven't done anything. I had to switch to the pen mode where I scribe each letter and then it puts lowercase letters in for me. Anyone know what's up with this?
Click to expand...
Click to collapse
I had that issue in GB... In ICS it seems to be intermittent- sometimes it just works others it doesn't...
And regarding the baseband, not sure about the Collective rom, but DAGr8's ICS rom displays the modem correctly on my Bell Note.
I also had the timezone issue- strangely enough when I disabled network time and timezone, I also stopped get random slowdowns and ANRs.
Sent from my SAMSUNG-SGH-I717 using XDA
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Hi, here are my thoughts;
1. Flash a CWM ICS modem(fixed it for me). If you cant find a modem use Dagr8's inital version of the ICS leak, it will successfully flash the modem(unlike the initial collective version(post 501 thread). The main point is to ensure you have the correct baseband(should not say unknown).
2. For now, dont supercharge the ICS leak until you have a stable running OS.
3. After fixing the baseband unknown issue(#1), reflash the collective post 501 ICS rom. It is stable, and the cleanup of the bloat was started already.
4. After installing #3, factory reset your phone.
At this point you should have a bloated, but error free ICS on your computer. Make a CWM backup, install titanium backup, and rip out the junk APK's(widgets, samsung/att garbage). Doing this will provide longer battery life and better performance.
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
studacris said:
No other wipe scripts are needed.
Factory reset BEFORE flash. The cwm script in the zip itself formats /system and /cache before it writes anything.
And the baseband unknown thing isn't a big deal. Its not that you don't have a modem at all, everything still works you get mobile data, its just the os doesn't properly report it.
I say if you like what you got, i say sit tight, we're working on the full ROM. You won't be disappointed
Click to expand...
Click to collapse
Would be cool if you guys could make a minimalistic style rom without all the makeup and cosmetics and focused on performance
We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme
most of us don't usually do minimalistic... once a stable rom gets out you can expect a variety of themes. Sit tight.
studacris said:
We've got the baseband unknown issue fixed in the full ROM. We just haven't released it. Still working on a couple things before we're comfortable sharing.
Click to expand...
Click to collapse
THanks Cris, thats all im waiting for to make the jump to ICS-----is the collectives official - unofficial ics dev thread.
Studacris said:
"We think its cooler to do BOTH
Cause the guys at Samsung must have left their seeing eye dogs at home when it came time to theme"
LOVE IT!... and CAN'T WAIT! Thank you for all you do... and have a few beers on me. PayPal confirmation number: 6RE28092GB801952P
fishing.laguna.madre
NoteI717
Powered by The Unofficial
Thanked you in the ROM threads, but again, very appreciated. Thank you.
Sit tight. what we got cooking is gonna be tasty
Same experience here
well done guys excellent base.... Having the same experiences as helios909...
Really looking forward to the the fully packaged version. Not experiencing problems with cpu speed set on boot.
Face unlock not work properly yet. Device hangs on reboot as reported. Auto update time bug exists. Baseband version unknown. Phone crashes on initial boot. But recovers.
New voice type engine is amazing. As demonstrated here.
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.