Slept the tablet thru the power down menu last night, and it wouldn't wake up. I held the power button to force a cycle, and now am getting constant core crash messages.
What's my fix? boot to root menu in clockwork and reflash the TnTlite ROM?
Life in LA said:
Slept the tablet thru the power down menu last night, and it wouldn't wake up. I held the power button to force a cycle, and now am getting constant core crash messages.
What's my fix? boot to root menu in clockwork and reflash the TnTlite ROM?
Click to expand...
Click to collapse
Reflash first, then try a clear cache and then a user wipe. If all else fails, try a SD re-partition.
* sigh *
the maintenance on this thing is getting to be like an italian motorcycle...
This is the life of flashing roms. Went thru this with my droid 1 but the gtablet isn't half as bad. I always clear cache and do a data wipe everytime I flash a new rom version that usually keeps the random FCs away.
Life in LA said:
* sigh *
the maintenance on this thing is getting to be like an italian motorcycle...
Click to expand...
Click to collapse
Like the motorcycle, a key is preventive maintenance
In our case, clearing cache and wiping data is the PM. When going from a same rom to a revision, cache should be all that is needed, but both if going to another rom (TnT to Vegan as example).
I'd say the key is backups. If you have a backup in Clockwork Mod, it's pretty easy to just restore if something gets screwed up.
But yeah, just to confirm, I haven't seen anything like this happen randomly to me though I've seen a few people report this happening, and for the past 3 weeks now on ZPad and Vegan, my G Tab has been more like a Corvette (fast and reliable) than a Ferrari (well, if you've ever dealt with a Ferrari, you know what I mean - fast but a POS).
uhg
Downloaded the latest build, installed it with no issues, but still got the close messages when rebooted.
cleared the cache, rebooted and am still getting this error:
"the process android.process.acore has stopped unexpectedly etc."
I would wipe the user data next. That might do it - if not, it's repartitioning the internal SD which almost always works.
I was getting the acore force closes repeatedly withing a day or two of a full wipe and flash. I was actually able to get them to stop by following the contact wipe procedure listed in http://forum.xda-developers.com/showthread.php?t=792691
Related
I'm getting mad trying to debug these random reboots. I'm getting a lot of them while the device is sleeping, without any advice. Sometimes it even halts and gets to a black screen, and I've to remove the battery to restart it, because just pushing the power button won't do anything.
Here's the last_kmsg:
http://pastebin.com/m79ba1a6f
May anybody please help me addressing them? I've already tried all the standard things, like wipe dalvik cache, fix_permissions, wipe and reinstall and so on. Of course I'm ready to provide any additional info, if needed.
Thanks and keep up the great work!
BUG: scheduling while atomic: suspend/7/0xc00b67f9
I think this is the main problem with this crash. Any clue?
try
I suggest trying to remove widgets before then reboot and wipe dalvik cache.. I was having similar problems when I did this it worked fine.. Dont really expect anyone to help you here, they get pissed when people ask simple questions.
Okay, I'm gonna try this. Thank you very much!
im using that rom at the moment, have been using cyan for ages but i can no longer use it, its so damn laggy get blank screens between different apps ,reboots its so unusable
Today I tried a full format and reinstall. Started from scratch, and installed on top of the default 1.5 rom, and it seems to work much better. I still have some rare RR issues during normal app usage, but at least it does not reboots itself randomly without being used.
Trying to clear dalvik cache didn't help, the phone still was unusable, so I decided to format the SD without ext partition.
I'll try it out for some days, if I still will see many reboots I think I'll try out the RA rom, I've read it's much more stable.
Just why exactly didn't you flash 1.6 android first like it's advised?
I have had a problem occur a couple of times today that has never happened before. I have an extended battery installed(3500mAh). After 2 hours of not using the phone this morning after I pulled it from the charger I noticed the battery was down to 86% when it should have been still at 95% or higher. About an hour after that I went to make a call and the phone would not unlock. In fact it would not respond to any gesture or button push. I had to pull the battery to get it to boot up again. That freezing up has happened twice today. Once with the extended battery and once with the stock battery. Should I wipe the data and start all over again? Or is there another solution?
Have you installed any new programs recently?
No nothing for a couple of weeks now.
Still having a lot of freezes. Should I go to the security settings and tell it to do a factory reset and then start over again with rooting and customizing?
just out of curiosity did you reinstall the location services?
No. The only things I added back in after the last flash were the ringtone trimmer, sound recorder, and the sprint tv.
one thing that I noticed when I had my phone hooked up to ddms looking at the debug log I had a RSS reader app that was add supported and every 30 seconds it would search for and dowload a new add. once I got rid of that app it seemed to help.
another thing that really helped was I downloaded an app called "overclock" it let me set my CPU to 528 when the screen was active really helping with the speed and how fluid the scroll in menu's is, but it also lets you set it to like 128 when the screen is off. seems to really help with battery life as well.
What is throwing me for a loop is that the phone sleeps like it is supposed and I have verified this with spare parts show I am not sure why all of a sudden the battery is draining much faster than before. As far as the lockups, they are just temporary freezes, it locks and I have to remove the battery to get it to reboot.
Well I wiped the data then flashed to the newest sprint rom(1.56) and then rooted again. I then wiped data again and then flashed to fresh 1.1 and installed my apps and setup my home screens. So far no problems and it seems to run a lot faster and smoother.
Quick off-topic question:
When you say "wipe your data" does that mean you rm the /data directory? Or what? Just curious
No. I used Wipe in the recovery screen.
i just did a upgrade on my hero too from fresh 1.0 to 1.1
when you select wipe data from recovery mode, besides wiping data with option 1, do you choose option 2 as well ? wipe dev something. i wasnt sure what the 2nd wipe option is for, so i did the first option only and it only took 2 sec to complete that step. my phone is up and running with fresh 1.1 without any issues, so did i do it rite ? just outta curiosity
The second one is the cache. I think it gets rebuilt anyway on the first boot with fresh installed.
My newly bought shiny LGO3D phone has a habbit of randomly shutting itself down no matter what ROM / Firmware i have on it.
I've tried stock, king ROM, and a few others. all randomly shutdown. i wouldnt mind if it had rebooted by itself at least it would come back on but it just goes off!
i reach into my pocket -- lo and behold the phone is off!
I've read lots of Optimus2x threads about a similar issue ... some blame the android system and some blame the hardware.
i wonder why there isnt a log in the android system describing an error or whatever?
can anyone help?
maybe your battery is a bit loose?
go stick some strips of paper at the bottom edge of the battery to make sure its nudged tight.
not sure, maybe a possible solution
i think i may have solved this issue...
what i did was this:
install CWM and reboot into the CWM menu.
i deleted everything. cache, delve cache, battery stats, everything thats deletable i did it.
i am currently using king_rom (which was doing the same problem for me to start with) and i can say the phone has been running ok for about 2 days now.
keeping fingers crossed.
usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it
Blezz said:
usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it
Click to expand...
Click to collapse
i never sacrificed the sdcard though its in there and its working fine.
I have Galaxy S with Android 2.3.4 JVR and it works like a charm - with this one exception: sometimes (too often) phone, contacts and messages (sms) keep closing. This happens usually within a second or two after opening up them. There's no force close message, it just returns to the home screen without any warning. If I reopen it, it usually does the same a couple of times, but eventually I get it to open.
At first I thought this must be a memory issue. However, I have Autokiller installed (my phone is rooted) and I have usually >100M free memory. Then I thought it must be Autokiller killing the dialer, contacts or messages apps. BUT: this happened also before I had Autokiller installed, so it can't be that either. The strangest thing is that I tried installing GO SMS Pro and GO Contacts + Dialer, and even they do the same thing occasionally (close immediately after I open them), so it isn't a problem with apps either.
I am bedazzled here, could somebody please help me? This starts to get really annoying, since the dialer, contacts and messages are the feature you normally use most in your phone!
I have the exact same problem! Somebody, please help
the phone app and etc. seem to be corrupt or something
try reflashing.If you keep getting the problem then revert back to your previous rom =/
Is there any way to try to replace only the phone etc. apps without flashing the whole rom?
from my experience no but you can try replacing phone.apk sms.apk etc with the previous rom's apps
The funny thing is that I have a stock 2.3.4 JVR, so it should be stable.
Plus, did I mention that this happens only sometimes? Sometimes they work ok. But this happens often enough to be annoying. You know, when you would have to make a quick phone call you have to open the phone app like 3-4 times, only then you're able to make it. I wondered if the the problem could still be in the dialer, contacts and messaging apps even if the problem occurred only sometimes?
In addition, the calendar app has done this a couple of times. Could it be that there's a conflicting app that's causing this? If so, do you have any suggestion what it would be?
Autokiller made my phone do some really funny stuff. After installing it i was having random reboots and apps crashing so i uninstalled and problem solved. You said it was happening before you installed it though so im just guessing that you need to either wipe cache and dalvik then reboot or do a full wipe and reinstall of your rom. When you do the full wipe go into mounts and storage and wipe system too
Hi and thanks for your comment. What are the effects of wiping the cache and the dalvik cache? Do I lose important data? Or can I do it safely? Sorry, I'm a bit of a n00b with android. I suppose you wipe the cache in download mode, right?
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Whitest said:
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
Click to expand...
Click to collapse
earthman5678 said:
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Click to expand...
Click to collapse
Okay, that sounds interesting - though I am not sure wheter a widget could cause this...
I am still running JVU but now with Galaxian Kernel instead of Chainfires root Kernel - flashed with SGS Kernel Flasher and still got root - and it runs very stable and fast 'till now. No more closing of phone, contacts and messages so far -.- since 2 days.
I'll tell you when it happens again, but so far it seemed to be a kernel issue for me...
I've been having the same issues with my Samsung SideKick 4G. messages would keep closing as I was typing them, I would lag and the key I pressed would "press again" like 15 more times, sometimes I just couldn't open a conversation, other times I couldnt answer phone calls cause the UI lagged.
That was all on stock firmware, and I got fed up with it so I tried to flash a custom ROM on it, and before I did that I had it OC'd to 1.2GHz which was actually pretty great. Needless to say, I screwed up on flashing the ROM and now I'm looking for firmware to odin back to stock. =\
I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.