Related
Hey guys.
I seem to be having an error message popup on my phone about 3/4 of the time once I reboot. (see attached image)
Usually hitting wait works, but sometimes i have to force close it.
I have JFs 1.41
I thought at first it was due to the fact that I removed several stock apps (amazon mp3, calculator & alarm clock)
I also removed my entire stock ringtones folder.
So I put everything back in its place.
However, I still have the same issue!
I also tried debugging with dalvik. Didn't get much...
Anyone know whats goin on?
TIA
EDIT: Also, just wondering if theres a way to reset the phone without losin all my apps. Other than backup, i'm trying to avoid installing all of em again ;0.
I get the same error on startup
Just to add my 2 cents... I have as well removed the Alarm Clock, and Amazon MP3, and the stock ringtones (but left the folders intact & put my own tones in). I am running JF1.41, and have never seen this message.
Did you do a Nandroid backup before you started messing with things? If so, you can simply restore that, otherwise.... You would have to re-install everything in order to do a factory reset.
Have you tried going to Manage Applications - Media Storage - and clearing the data?
I would try doing a full wipe of the phone and see if the problem continues.
Just my 2 cents
daveid said:
Just to add my 2 cents... I have as well removed the Alarm Clock, and Amazon MP3, and the stock ringtones (but left the folders intact & put my own tones in). I am running JF1.41, and have never seen this message.
Did you do a Nandroid backup before you started messing with things? If so, you can simply restore that, otherwise.... You would have to re-install everything in order to do a factory reset.
Have you tried going to Manage Applications - Media Storage - and clearing the data?
Click to expand...
Click to collapse
Yea I've tried clearing the data. Its not fixin it tho. I have several nandroid backups. I would do a wipe but wouldn't that get rid of my apps?
Thanks guys.
restoring a nandroid backup to a time when you didn't have this issue would be the best bet, you would only lose the changes you have made since that backup.
topdnbass said:
EDIT: Also, just wondering if theres a way to reset the phone without losin all my apps. Other than backup, i'm trying to avoid installing all of em again ;0.
Click to expand...
Click to collapse
Well I had my apps and cache on my SDcard and after updating to JF 1.41 i had to do a wipe to get it to work, but after it was up and running I just replaced the mountd.conf and init.rc files and recreated the symolic links again and rebooted and all my programs were back. Just thought I would share cause this way pretty much worked for me to not have to reinstall all my apps... I'm still pretty new to all this so maybe there is a better way.. but this worked for me...
Unusual...
First I did a nandroid restore to the time a little after I got JF's 1.41. Everything was fine at first. I installed all of my apps. Tried to reboot a few times, and bam, I see it again.
In a rage--I wipe my fone from recovery mode. I then use MyBackup to restore all of my settings and apps.
I finish, and then i try a reboot and BAMMM ****in android.process.media is not responding.
Then I tried to reboot 3 more times wthout a problem and then the 4th time gave me the same problem.
Can anyone else whose having the same issue tell me what apps theyve recently installed?
Ive figured it out. But still stuck.
The problem was that i setup a symlink for my market cache to my sd card.
I removed the /data/data/com.android.vending/cache folder and my sd cards linked cache folder.
I then made a new cache directory in com.android.vending however I noticed that it wasnt working properly. It wasnt filling up with cache when i used the market.
I removed the symlink so why wouldn't it, right?
So I chmodded it.
I tried to chown it but i keep getting back unknown user app_5 (the markets ID)
I'm stuck please someone help me out here, and hopefully we can even get the market cache properly directed to my sdcard in the process.
THANKS!
topdnbass said:
Ive figured it out. But still stuck.
The problem was that i setup a symlink for my market cache to my sd card.
I removed the /data/data/com.android.vending/cache folder and my sd cards linked cache folder.
I then made a new cache directory in com.android.vending however I noticed that it wasnt working properly. It wasnt filling up with cache when i used the market.
I removed the symlink so why wouldn't it, right?
So I chmodded it.
I tried to chown it but i keep getting back unknown user app_5 (the markets ID)
I'm stuck please someone help me out here, and hopefully we can even get the market cache properly directed to my sdcard in the process.
THANKS!
Click to expand...
Click to collapse
try using the numeric id with chown instead. i.e. 10005 (not positive if it will work.. just something to try)
AHhh Yay JF ILY! That worked . I feel like a retard now.
The cache appears to be filling up as normal. The error isnt gone yet tho.
The question still remains. What causes that error?
How could i stop it?
The crashing process has the same gid/uid as Android.providers.media
it seems to be an app. I wiped and then I reinstalled 1.41. Then I installed all of my apps using mybackup. I made sure to do nothing else after, and I still got it.
Its either JF's 1.41 or an app.
How can I find out
Process of elimination. Wipe the phone again, instal jf's 1.41 and boot the phone. If you don't have the error, bingo, it's an app. Then, tedious as it may be, install the apps 1 at a time and reboot after install to see if you get the error.
Yeah I have done that.
However, its reallly hard because sometimes itll go 4-5 boots without a hitch, and then suddenly itll happen.
Then at other times it'll happen nearly every time.
I have about 65 apps. That's 4-5 boots, after installing each one.
So that would mean HUNDREDS of boots. At least 200.
I've been thinking that maybe its a problem with the MyBackup app.
What if the fact that mybackup overloads the phone with 20-30 installations at a time is whats causing the issues.
Well i'm off to error and error. I mean trial and error.
I've figured it out!
It's something to do with my wifi connection.
I think its that my dns's are from opendns.
Basically whenever my wifi is active when I turn on my phone i get that error.
If i turn it off and reboot into 3g, i never have a issue.
That's why it was so random before and I couldn't find any patterns!
I'm gonna call my ISP tomorrow, but anyone know what it could be?
I don't think it has anything to do with OpenDNS. I use JF1.41 RC30, MyBackup, and OpenDNS and never have any problems...
Hmm, do you have your router setup for opendns or your phone.
I have issues where i cant get my damn router to give out working IP's, so I
need to setup the phone for a static ip and dns.
I think that if I could get it to automatically get an IP i'd be set.
EDIT: Also, could it have anything to do with the fact that I have wpa personal security (AES)
Im having a similar problem but my error is slightly different
"com.google.process.gapps" anyone know WTF that is
Its the G Talk service.
If you dont use that app you could try removing it and see if that does anything ..
Since this has been bumped, i'd like to add that it still happens whenever I'm on wifi. Really blows
topdnbass said:
Its the G Talk service.
If you dont use that app you could try removing it and see if that does anything ..
Since this has been bumped, i'd like to add that it still happens whenever I'm on wifi. Really blows
Click to expand...
Click to collapse
Care to explain how?? Im a serious noob lol
Greetings people!
Yesterday I got this message while booting up my TP (latest official ROM):
"The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press END to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings"
However apart from that message, phone works flawlessly without any noticable change in speed or stability! The only apparent problem is that it takes a while longer (about 10 seconds) to boot up because of that message. I tried a couple of backups, problem was solved at first, but returned later...
I do take daily backups, but since I hardly monitor my phone when I reset it, this problem could have been caused by an app or reg entry a while ago... and searching for the appropriate backup will be a pain in the ass.
Since there's no change in speed or stability, do you think it would be wise to keep using the phone as is, or is it possible this would cause further problems down the road?
Any other way to troubleshoot it (at least to find the program that's causing this) other than a hard reset?
Edit: couldn't wait so I reverted to a week-old backup, installed back most of my applications, and it seems to be fixed (for now)
Update! I just tried a new SD to try XDAndroid, and guess what, the error disappeared!
So there must be a program I had installed in the storage card, possibly trying to start a service or something on every reset... and failing.
Is there a way to troubleshoot this? Maybe through SKTools or anything similar? I have a ton of apps installed into storage card and it will be a pain in the back cover to try by trial-and-error.
Thank you in advance
edit: inserted my old storage card again, error did not appear, problem solved! At least for now
Still if anyone knows how to troubleshoot this, please let me know
Update: Seems this error occurs every time I use SPB backup.
Yesterday, after a scheduled backup, the error came back. To troubleshoot this, I removed the SD card, did a soft reset, the error was gone! I took another manual backup, and again, the error came back.
So there must be something happening with SPB Backup and my SD card. Probably messing with files on the SD, or the driver or whatever (no idea there, I'm a total noob when it comes to software).
Moved the issue to the SPB forum
I have this message to, but I have never used SPB Backup
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
akpidis said:
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
Click to expand...
Click to collapse
Well I tried that just to see what would happen and I did not get the error message. So it is something on the SD card, but booting without it is not an option for me as I have several boot-start apps that are housed on it.
Perhaps one of those apps is broken?
As far as my case goes, I kept on using it for three months after the error appeared, without noticing any lag or issues at all. The only downside was that it took me three minutes to boot up, something I got used to.
If that's no big deal for you, I'd suggest you just leave it as it is for now, and check for lagging or specific applications failing (maybe one of them will be the app that's causing the problem?). If nothing happens down the road I think it could be safe to leave it as it is.
Now, if you can't stand this, I guess the only practical solution would be a hard reset. You can always play around with removing/reinstalling those apps you mention (or even better, installing them in the phone's memory) to check if and which one is broken, but I can understand that this not only will be a huge burden, but you may come to the conclusion that no specific app is causing this and something went south in the OS.
Personally the only apps which include a boot-up service I have installed into my SD are Football Monitor and PocketWeather. I tried removing both of them them back when I first had that issue, it didn't work...
Sorry I couldn't help more :/
As I suspected early on the issues boil down to corruption within the User Data or Cache partitions, less often on the system partition due to an unexpected shutdown of the device. Shut on these devices need to follow the proper shutdown routine as any linux environment. Following this best practice will ensure that all data is written out to its corresponding file system by flushing all cache, unmounting the file system, etc..
Here are the culprits of why we see so frequent random Force Closes, Market Resetting, etc. ultimately resulting in an unclean shutdown, corrupting some data.
1. The button we use is also a forced off button. Typically if you hold it down too long you are powering off the device.
2. Some times when in sleep mode you see the Viewsonic logo upon starting - that means that the system shutdown (most likely crashed).
3. If your running Vegan your hitting the reboot.. I dont know for sure but I suspect this is NOT performing a clean shutdown... (I dont have a copy of the source)
Anyway... wanted to pass this on... as last night my data partition became corrupt after using the Reboot function on the Poweroff menu of Vega 5.1..
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
roebeet said:
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
Click to expand...
Click to collapse
I have been on stock since I got the device just moving to the newer versions when they come as OTAs and have never ever had to mess with my partition, so I don't THINK the issue is in the stock software. In fact, the only problems I've ever encountered were when I used the enhancement pack, in which case my screen started to become unresponsive and the calibration.ini I was told to try did not work. Since then I went back to 3389 and the device has been perfect ever since.
I could be wrong though and just very, very lucky....here's to hoping. Another thing to consider is maybe the memory is going bonkers for some reason. I've had flash memory that lasted forever and I've had flash memory that has gone wacky over a period of 6 months....even a wipe by the utility designed to do it doesn't fix it properly. I don't know how CWM wipes or partitions the memory, I do know there's supposed to be a special way to do it.
If it's not faulty memory off the bat, then that leaves something in the 'extras' being put into these ROMs. Maybe some of the newer tegra drivers or some coding to make the ROMs faster - I'm just saying, can't leave any stone unturned.
Has anyone that has stayed loyal to stock encountered these issues? We have to ask that question I think. Then we ask how many of the people playing with ROMs are seeing the issues, this would include people that have used CWM to partition and mess with their mounts initially.
I can say I've never seen data disappear from my internal memory or my SD and I can also say I've never seen multiple FCs except after putting in the enh. pack (keep in mind I got my tab on Dec 20something, so I had 3053 and then 3389 soon after).
The first sign of anything being 'corrupted' on it's own at stock and I'll be sending mine back. As an owner of Android since Android's been around, I've never had my G1 or MT4G (or any smartphone before it) become corrupted due to not being shutdown or reboot properly and while this is a tablet I think the fundamentals should be the same. Pampering 'faulty' memory is a risk. You can wipe and re-do all you want, but if it's faulty it's going to stay that way.
Ive done that but I guess you can say unfortunately I have had only clean shutdowns since then... The last corruption I had I formatted my data and cache partitions before I ran logcat.... Of course thought of that afterward....
Generally if any has FCs, etc. etc. run a logcat and post it here... we will be able to confirm this...
We could change the way the partitions are created and add a sync which will further reduce chances BUT will take a performance hit...
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I reviewed the out of the box framework source on the google GIT and technically if a reboot command is given a clean shutdown is performed via the framework... but the widget on the shutdown screen I suspect is not calling the method properly or is not being called at all... All speculation at this point... But for sure there is corruption occurring..
Since the last corruption I switch over to pershoots kernel... Even though his kernel seems to be a little slower he seems to have included the latest drivers which other items relate to data integrity (im reading into the release notes).
NEO: The first thing I did when I got my device install CW, Vegan... Updated Kernels also... Never had an issue until the first time (yes about a day ago) I used the reboot feature of Vegan. That corrupted my user data. I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
But again.. between the wrongly placed power switch, the unprovoked reboots (ie viewsonic screen showing when trying to wake up the device) and the reboot button possibly not performing a proper shutdown will sure increase the chances in a wider distribution of users. So it may not be a CW issue and just some poor design.
When I have time today I will verify if the reboot function performs a clean shutdown... if anyone has the time please post the logcat... Im going to be running around today and will try to get to it..
watson540 said:
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
Click to expand...
Click to collapse
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
Click to expand...
Click to collapse
AFAIK they're running yaffs ATM. Next move is to ext4...
Read some articles about this several weeks ago, apparently many apps do not properly flush file caches. One of the articles was a Google developer post about file corruption along with their API method which did a cache flush prior to a close, then a bit later was the Google indication that they were planning to move to ext4 FS to further help alleviate the problem.
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
Click to expand...
Click to collapse
That's my point. How many times since we've had our Android and smart phones have we had situations where they are turned off or rebooted without the proper procedures? Power drains till they die, they drop and reboot, we clog them up with stuff or some app drives them nuts and they reboot or shut off....Yet you rarely if ever hear about a phone's data being 'corrupted' with stock software. Sure it may happen with official OTAs etc, but never just off-the-bat like what's happening with the G-Tab. But it's not happening to everyone either so I'm just looking to see if there's a pattern.
Even since the G1 and newer phones, you don't really hear about or see file corruption issues on stock software with these phones. It's when users start going to ROMs that you hear of issues cropping up. That's not to say it doesn't happen at all at stock, I just think we're seeing it in a more concentrated fashion here because of all the formatting, re-partitioning, etc. At first you hear, 4GB is a great partition size, then you hear there are problems so move to 2048, then you hear 256MB swap, then no swap since Android doesn't use it. Then dataloop for speed, then no dataloop because of critical issues. Rules and instructions change almost on a daily basis. I think it's more than these poor flash drives can take I find sometimes it's good to keep it simple.
I owned a Vibrant for a while...decided it was a PoS when at stock I was seeing bad lag (because of Sam's terrible FS). People said...do the speedhack, it'll be fast!, but what was the caveat? Having to reboot the phone almost weekly, sometimes several times a week, and people were seeing what? Data corruption. That's not for me. Give me something that is lag free (doesn't have to be a bullet train, just don't skip on video or audio and make sure my live wallpaper and drawer animation is fluid and I'm happy!). Point being....keeping it simple may help to alleviate some of the issues. If people are seeing these problems with stock, then you're absolutely right and it would be a point of contention that the failsafe isn't working right.
Otherwise it seems the stock OS on these things are able to self correct in most situations and it may just be some of the many tweaked features in these ROMs doing something it shouldn't - or, I may just be very lucky indeed.
I'm still dying to get the OTA - I haven't seen one since 3899 yet.
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
Hi, I have a samsung galaxy tab s2 the 9.7 inches one, but lately some apps have been crashing or having errors, chrome for example throws that snap somethjng wrong, perfect viewer sometimes gets stuck on an image and I cant chnge it, but all menus work, several apps keep crashing as well.
I have it with official firmware, never touched it, its rooted with magisk since before the problems started, apps that use root are file explorer, vanced manger and an app to disable some samsung bloatware.
I dont know how to troubleshoot android, on pc I would check memory and hdds, but theres nothing lkke that kn android that I could find.
I think it could be memory or storage, but everything Ive downloaded or copied/moved hasnt have any problems or errors. Or something is corrupted in the system, or I dont know what else or how to check.
What would you recommend to fix it? Hopefully starting with less drastic, as in less data loss, factory reset, flashing an original rom or somethjng.
The device is aSamsung galaxy tab s2 9.7 with android 7 with lean launcher.
All help is appreciated.
I believe this were an common issue for Android 7 and below !
and you have an old device and android which I believe it's no longer supported by the most of developers.
try to flash any custome roms & kernels if available.
If apps are randomly crashing then the reason might be it's caused by an update of Google's tool called Android System WebView.
Abdullah.Csit said:
I believe this were an common issue for Android 7 and below !
and you have an old device and android which I believe it's no longer supported by the most of developers.
try to flash any custome roms & kernels if available.
Click to expand...
Click to collapse
But it hasnt happened before until now, what would it fix using a custom rom instead of the original?
jwoegerbauer said:
If apps are randomly crashing then the reason might be it's caused by an update of Google's tool called Android System WebView.
Click to expand...
Click to collapse
I had that problem with my phone, my tablet never got that update.
Thanks
Clear system cache...
Wiped dalvik and system cache, but still having the same problems.
Thanks
totopesce said:
Wiped dalvik and system cache, but still having the same problems.
Thanks
Click to expand...
Click to collapse
Try using the stock launcher.
See what apks are running and cached right when this happens is it may give you a clue.
I would completely backup all critical data now.
Android is normally very stable.
Scan with Malwarebytes. If you can't find the root cause, suspect a virus, rootkit etc.
This is rare but can happen.
Karma Firewall can help you to see what's accessing what and how often. It uses almost no battery or resources, freeware, adfree, a near perfect little app.
Cant remove lean launcher it gets stuck in android is starting and it doesnt let me change to stock, installed nova just to check if it was lean and still the same problems.
Installed malwarebytes, had to run the scan several times cause it kept crashing, it completed and it didnt find anything.
Installed karma firewall and will see if I find anything.
Thanks
totopesce said:
Cant remove lean launcher it gets stuck in android is starting and it doesnt let me change to stock, installed nova just to check if it was lean and still the same problems.
Installed malwarebytes, had to run the scan several times cause it kept crashing, it completed and it didnt find anything.
Installed karma firewall and will see if I find anything.
Thanks
Click to expand...
Click to collapse
Figure out how to get the stock launcher back.
Any 3rd party app you can't uninstall is already malware. Check Device Administrators to see if it's registered there. Nova is no saint either.
If you can't resolve it error on the side of caution that it is malware and nuke it. Sometimes you never find out which one it was... getting rid of it is all that matters.
Sorry, what I meant was that after uninstalling it it got stuck in androiid is starting, somehow I lost the stock launcher, so it got stuck with no launcher. Found the launcher that came stock, installed it and uninstalled the other 2.
Apps are still crashing, I deleted all apps that I dont really use.
totopesce said:
Sorry, what I meant was that after uninstalling it it got stuck in androiid is starting, somehow I lost the stock launcher, so it got stuck with no launcher. Found the launcher that came stock, installed it and uninstalled the other 2.
Apps are still crashing, I deleted all apps that I dont really use.
Click to expand...
Click to collapse
Lol, that can crash it for sure.
See if you can find a common apk between the effected apps. Any recent system app updates?
New or uninstalled apps?
A system apk may have gotten corrupted.
Android is pretty good compared to Windows when uninstalling apps but occasionally a poorly designed app will screw it up.
It's just about factory reset time or your equivalent.
If it an old load that's probably best anyway.
I haven't reloaded in almost a year but I'm ready to go at any time.
Takes me about 2 hours to get it back within 99%. All the data I need for a full restore is on my SD card otherwise it would an additional 6-8 hours to restore the SD card data as well.
If you don't have a complete reload plan that saves all your critical data no matter what, implement one now before you get burnt.
Those stories are too common here
Dont remember when it started, cause at first it was one app from a github that was having problems, then yesterday magisk started and when I got that working it all when to hell.
The app that I use most has a backup/restore file that I saved on my sd, what do you use to backup/restore?
I would think that some backup solution could bring the problem back or am I mistaken, like if you fully restore something corrupted it should still be corrupted?
A factory reset could be corrupted as well? I mean after a factory reset, assuming its software, could it still have the same problems?
Though I dont really have any critical data on the tablet its mostly for browsing, youtube and reading comics. Still its a bother to re configure everything xD. IIRC I think its only been factory reset once.
Thanks.
It's unlikely the factory reload image is corrupted.
The current one your using likely is.
Other than apps that allow you to back them up like Poweramp or perhaps bookmarks, most app data I would write off just in case that was connected to the current issues.
None of my database is on internal memory except DCIM and downloads (both I back it up at least monthly). Critical apps like Poweramp are backed up on the SD card as export backup files.
The Poweramp setup would literally take a week to recreate. Most apps you can throw together rather easily.
All the SD card data is then again backed up at least twice to other separate drives.
I will try Samsung Smart Switch to restore home settings and see how it does on the next reset.
If you issues are of unknown origins being conservative about what you allow on the new load could save you more time in the long run.
If you unintentionally import corrupted data you'll end up doing it over again.
Or do so if the reload time isn't that great and is an easy write off for you.
Fun times... especially if the reload doesn't fix it
Did a factory reset and problem solved, took me less time than I thought to get my most used apps ready to go.
Thanks for the help.
totopesce said:
Did a factory reset and problem solved, took me less time than I thought to get my most used apps ready to go.
Thanks for the help.
Click to expand...
Click to collapse
Yay! Success!
And a minty fresh OS load.
Load apps and especially updates over time to see if one these were the cause.
Forced reloads are rare but they happen usually caused by a rogue app screwing up boot or a malware infection. Otherwise you can usually track down the root cause which is preferable to avoid it from happening again.
Lazy techs misuse factory reset a lot
Will do that, install apps just as I need them and try not to instal a bunch at once.
I had a problem with an sd card and sent it to samsung, they did just that factory reset it and gave it back with the same problem, and they dont even let you know so you can back your stuff up, just lucky it was fairly new at the time and I had the sd card with me.
totopesce said:
Will do that, install apps just as I need them and try not to instal a bunch at once.
I had a problem with an sd card and sent it to samsung, they did just that factory reset it and gave it back with the same problem, and they dont even let you know so you can back your stuff up, just lucky it was fairly new at the time and I had the sd card with me.
Click to expand...
Click to collapse
Sammy tech support sucks.
I'm using the Lexar .5 tb V30 card, just format in phone and it's good to go. Zero issues for $64.
Been using it for over a year now. Play movies and music from it all the time from it flawlessly.
Been using Lexar flash cards for over 15 years and all cards are still functional. No failures or card related issues at all. I like that brand a lot.