Alright, I've been using Fresh Toast for about two weeks now and love every second of it..The phone is incredibly responsive and everything I could want in a Hero. But I've run into a few problems/questions.
1. What does the option "Fix apk UID mismatches" option do in recovery? I've searched and it seems the only explanation is "it does just that" but I don't know what that is or means..
2. More often I've noticed I've had the mobile network not responding and had to toggle the option off/on for things like internet to work, but after the toggle it works just fine. It hasn't really started to be annoying till recently. Is this a problem in 2.1? Or Fresh Toast?
3. Possibly in conjunction, my phone has restarted 3 times by itself today..just sitting on the table. What could be the reason for this? I haven't installed or changed anything for at least a week, and it just started happening. It can get to be annoying because it takes a few minutes to boot up and a little inconvenient..
From what I understand, the apps and stuff have ID's which the phone can confuse sometimes, causing force closes of stuff you think should work. Fixing the mismatches helps with the force close problem some have. This is based off of knowledge I have gained from using th search button, but I am not rude enough to tell you to do a search when I am already typng you a message.
The random rebooting sounds like a problem you might want to take to sprint...
and I personally have been having some issues with mobile network using regawMOD lately... I am not blaming it on the ROM, jsut letting you know that I am using a different 2.1 ROM than you... mobile network locks up, doesn't respond and I have to toggle airplane mode to make it work, or it's just murderously slow compared to other times, andall while in the same location: my computer.
the random rebooting may be your phone unable to handle high frequencies... use overclock widget, and bring it down a notch to 710 or 691, and try that. The uid mismatches, I think, is a linux thing... the uid of a file is its permissions, aka read, write, execute, etc., but don't ask me how they get messed up and need that (you root your phone through adb? remember typing chmod 755 blah blah? the chmod command changes uid's, and the 755 is telling it what permissions to give it, but I don't remember the breakdown of the number, still learning linux myself)
Related
My CDMA Hero started rebooting randomly during the last week or so. I uninstalled all recently installed applications and the problem went away.
However ...
This has happened more than once, and it takes a lot of time to track down the offending app(s). I really want to know how to troubleshoot if this happens again.
If this were a Windows computer, I would go and get the minidump file and run it through windbg and it would suggest what module had caused the fault.
Is there anything like that for Hero crash / unexpected reboot? If not, what approach would you suggest for investigating these incidents?
Thanks,
Chris
Running DamageControl 2.08.1
Best thing i know to do is to run logcat with adb and try to recreate the problem.
Hard to repro...
Thanks, but the problem was so sporadic ... it would go hours, or even days, between reboots. Is it possible to use something like logcat to get the log files from *before* the current bootup?
im not that familiar with logcat, just search the string "Logcat Hero" on the Xda forums and you should be pointed in the right direction
Is there anything like /var/log/messages?
Thanks again. I went and looked at the logcat documentation and there are some options to get different kinds of output. However, I reset the phone (simulating a crash) and when that happened, the logs were cleared, so that there were no log entries visible via logcat that predated the shutdown.
Does anybody know where the actual log files are kept? There isn't a /var/log/messages or anything like that. Where do I find files equivalent to the "normal" Linux /var/log/messages?
Thanks,
Chris
*2nd EDIT*
Okay now I don't feel so dumb, I renamed the otacerts.zip thing but i am still getting reset
I did find an application that is call BN authentication service. I can't uninstall it from the normal App installer, anyways to get around this? Like ADB
*EDIT*
Ha I feel so dumb, I just needed to reboot, then change the names. So after i changed the names I rebooted again and its all good now
Thanks eyecrispy
* original*
I have a rooted nook color with a stock 1.0.1 rom, CWR, and a over clocked kernal. I have only 1 real problem, I guess besides not being able to download from the marketplace - my nook keeps on getting reset by B&N! They don't unroot it, and my recovery is still intact, but it really sucks not being able to connect to their shop. It's not that I would use their shop it's just that I accidentaly press it every now and then and it resets my device. I have to back up my device once everyday to make sure nothing gets deleted because sometimes, even when I don't press the shop button, I don't even have to press anything, it resets the device after its been connected to wi-fi for a while. Like the other day, i just set it down to go to the restroom, I come back to find it at the Android setup or the quick setup selection page. When I select Android setup when I press the little android nothing happens. When I select the B&N quick setup it, i can do that no problem. So now I just turn it off from there and load my back up through CWR.
Anyways, is there anyway to stop it from connecting to the B&N authentication service or something? I have seen people with similar problems, but no one seems to have it happen to them over and over and over again.
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
eyecrispy said:
Plenty of folks have reported this continuously happening. Have you disabled OTA updates?
Sent from my Nook Color
Click to expand...
Click to collapse
Really? All th threads I have read people say it happened once but after a reboot it was fine. Maybe I just missed it. If you could please tell me how to disable OTA updates that would be a big help. Thanks
*EDIT*
Found what you meant, I am trying to use Root Explorer but am having no luck. I gave it superuser permissions yet it still wont let me changes any system files
This turns out to be a crash bug in Android see last post
While i was researching ways to maximize the battery life on my captivate I came across a setting in the tasker wiki that would help me log the life of my battery.
I had already set up juice defender and other ways to let tasker turn on and off battery draining settings like GPS and WIFI and thought that this would be a good way to track on a day to day basis how much life i was getting out of each battery.
Here is what i found. The day after i set up the tasker profile i began watching results. Around 11 am the next day my phone began to loop in reboot. it just went right to my bootanimation and then home screen, boot animation, home screen....
I thought nothing of this as i flash roms often and was beta testing some stuff at the time. I proceeded to flash stock ---> flash custom rom. what i i had to repeat this process a few times because it continued to reboot. After a few flashes i became stable. the following day at around 11 am my phone began to boot loop again. this time i flashed stock and left it there only to begin looping again. i turned the phone off for a while and then flashed stock--> custom rom. It looped again.
this time i brought the phone to a device support center and had it replaced.
with the new phone i use no settings or backups from TiBu except for a few apps like handcent, takser, angry birds and a couple other games. at this point i thought that my old phone was just worn out from the many flashes. Two days after getting the new phone and installing all apps (except the few apps like tasker) my phone began to boot loop at 11AM. this time i flashed to stock and it began to boot loop again. I repartition and flashed again and it became stable. Until the next day at 11am when it began to boot loop again.
i returned to the device support center with a stock phone in boot loop.
this time I have not used a setting from tibu backup but have returned all aps to almost the same as before (the best i can by memory)
day one i Ran stockfor a day.
day two i ran the same custom rom/kernel combo.
day 3 i ran everything with the apps set up and used the same battery that was in from the last time it looped.
The only Thing that was the same from both phone that looped what isn't in my newest phone is that tasker setting.
I am almost 99% sure that this setting did something to the file system at low levels which is unrepairable by flashing.
Is this a bug? i do not know, I reproduced it twice but do not think that a device support center will replace a third device for me.
If anyone is/has ran this profile with no problems than I can let this go as unsolvable.
If anyone is willing to test this setting and can reproduce the bug then i think we will have something to take to Samsung regarding a system bug that is unrepairable at user level.
here is the link for the profile
i followed this setup exactly as stated except here Write File: File "Batterlog.txt" i used "BattLog.txt" im not sure if it makes a difference but if you are going to set this up please try it using BattLog.txt
here are the steps
Code:
1. Make up a new profile, context: Power: Battery changed, priority normal -> done.
3. Add task Alert: Flash: Text "%BATT % %MEMF", If checked "%BATT !~ %BATTPREV" -> done
4. Add task File: Write File: File "BattLog.txt", Text "%DATE %TIME %BATT", Append checked, If checked "%BATT !~ %BATTPREV" -> done
5. Add task Variable: Variable Set: Name "%BATTPREV", To: "%BATT"
I guess everyone must think that i indeed did find a bug in the filesystem because not one person has come forward to try this out. If I am wrong at least you have yourself a very nice way to track you battery usage.
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
tiuk said:
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I am not attempting to recreate at this time. I will be when I have a replacement phone. If this is indeed a fs bug i can imagine anyone who does not want their phone aymore could use this setting and go into infinite loop and get a replacement. The does not require root and can be used on any firmware. Samsung would have to react.
so after running the new phone for a week i got the boot loops again today at 11:08am
i am trying to see if it is battery related as I DID NOT have the tasker setting in place.
here is the log if anyone wants to try and help solve this. i have other batteries i will be trying this week. (everyday until i fix it) the problem is though that if the filesystem is damaged than testing on this phone is useless.
http://dl.dropbox.com/u/17699865/android_report1298308267139.zip
I solved the bug bug cant fix it.
follow the link to my report.
anyone able to reproduce?
i have been able to send the message to myself but it always arrives in 2 part.
goo.gl/wCrlp
Good evening,
My phone (T-Mobile Note 4 on stock 4.4.4, rooted) worked just fine until I froze an app I shouldn't have. When I boot up, everything loads just fine, about 20 seconds in, I get two quick vibrations, and I'm back to a "Samsung" startup screen; the process repeats ad infinitum. I attempted dirty flashing the stock ROM, as well as restarting the phone in safe mode, but it still does the same thing. I'm reasonably confident that if I defrost apps (all of them if need be), the phone will stabilize, but the window of opportunity between boot loops is too short to do so within Android.
Is there a way, within TWRP (or another recovery environment), to defrost apps? Since TWRP is still functioning fine, I am thinking that this may be repairable in the recovery environment...or am I stuck doing a full wipe and restoring data using TB or similar?
Thank you for your consideration.
Joey
voyager529 said:
Good evening,
My phone (T-Mobile Note 4 on stock 4.4.4, rooted) worked just fine until I froze an app I shouldn't have. When I boot up, everything loads just fine, about 20 seconds in, I get two quick vibrations, and I'm back to a "Samsung" startup screen; the process repeats ad infinitum. I attempted dirty flashing the stock ROM, as well as restarting the phone in safe mode, but it still does the same thing. I'm reasonably confident that if I defrost apps (all of them if need be), the phone will stabilize, but the window of opportunity between boot loops is too short to do so within Android.
Is there a way, within TWRP (or another recovery environment), to defrost apps? Since TWRP is still functioning fine, I am thinking that this may be repairable in the recovery environment...or am I stuck doing a full wipe and restoring data using TB or similar?
Thank you for your consideration.
Joey
Click to expand...
Click to collapse
Recovery still functions because that's what that is, a way to 'recover' your phone. That said, if you used TiBu within your ROM to freeze an app, that's how you defrost it. I would imagine you are stuck doing another install. That's what I did when I made those mistakes with TiBu.
Basically you can't really run apps in recovery, you run zips that add and remove things to different positions.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Recovery still functions because that's what that is, a way to 'recover' your phone. That said, if you used TiBu within your ROM to freeze an app, that's how you defrost it. I would imagine you are stuck doing another install. That's what I did when I made those mistakes with TiBu.
Basically you can't really run apps in recovery, you run zips that add and remove things to different positions.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I know the recovery environment is a bit of a different animal; I certainly wouldn't expect TiBu to do the job. More what I'm getting at is, the way I understand how app freezing works (and it's entirely possible that I'm wrong in this regard), it effectively sets its chmod to 000, so that the file system prohibits the binaries from being able to be accessed. If it's a matter of recursively running chmod on a particular directory, I know that TWRP makes it possible to run terminal commands, so it would be a matter of running a 'chmod 755' on the correct folder to ultimately do a defrost, which can be done from a shell prompt.
That's more the thought I had, though I'm about ten minutes away from saying "screw it" and reflashing...but I'd rather not, if at all possible.
Joey
voyager529 said:
I know the recovery environment is a bit of a different animal; I certainly wouldn't expect TiBu to do the job. More what I'm getting at is, the way I understand how app freezing works (and it's entirely possible that I'm wrong in this regard), it effectively sets its chmod to 000, so that the file system prohibits the binaries from being able to be accessed. If it's a matter of recursively running chmod on a particular directory, I know that TWRP makes it possible to run terminal commands, so it would be a matter of running a 'chmod 755' on the correct folder to ultimately do a defrost, which can be done from a shell prompt.
That's more the thought I had, though I'm about ten minutes away from saying "screw it" and reflashing...but I'd rather not, if at all possible.
Joey
Click to expand...
Click to collapse
I see what you mean, I tend to forget that because I go the 'up it' route and clean slate it. I've done a ton of freezing and deleting the wrong apps on many different phones. And being the tire of person that used to flash a new ROM every three days, never really bothered me.
Sent from my SM-N910T using Tapatalk
aaldiar said:
I see what you mean, I tend to forget that because I go the 'up it' route and clean slate it. I've done a ton of freezing and deleting the wrong apps on many different phones. And being the tire of person that used to flash a new ROM every three days, never really bothered me.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I loved being able to do that. The reason I've gotten more wary about reflashing ROMs is the fact that I've got about 62,000 text/MMS messages now. I'd like to keep them, but thus far I haven't found an app that will do some sort of "autoarchive" app function where my 200 most recent texts are treated normally, but the rest are stored in an independent database which itself works similar to the 'online' UI. Resultantly, my restore operations take 5-6 hours, and because Google has thus decreed that only one SMS app can write to the database at a time, I'm stuck keeping my phone in airplane mode during that time, otherwise texts that come in will be delivered to /dev/null...so ultimately, if /that/ problem can be solved, I'd love to get back to being able to be flash happy again. At this point, though, I'm clearly stuck...but if anyone else can chime in, I'd greatly appreciate the knowledge!
Joey
voyager529 said:
I loved being able to do that. The reason I've gotten more wary about reflashing ROMs is the fact that I've got about 62,000 text/MMS messages now. I'd like to keep them, but thus far I haven't found an app that will do some sort of "autoarchive" app function where my 200 most recent texts are treated normally, but the rest are stored in an independent database which itself works similar to the 'online' UI. Resultantly, my restore operations take 5-6 hours, and because Google has thus decreed that only one SMS app can write to the database at a time, I'm stuck keeping my phone in airplane mode during that time, otherwise texts that come in will be delivered to /dev/null...so ultimately, if /that/ problem can be solved, I'd love to get back to being able to be flash happy again. At this point, though, I'm clearly stuck...but if anyone else can chime in, I'd greatly appreciate the knowledge!
Joey
Click to expand...
Click to collapse
HA! What a coincidence! I use evolve sms. I backup my texts regularly to the cloud. I use Dropbox but it also allows google drive.
As far as archive goes? It allows you to delete the previous backup add you upload. I don't know if it archives recents vs everything. I delete the backup every time I upload the latest.
Sent from my SM-N910T using Tapatalk
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater