Hi,
I have a TF101 that's 2 years old, Android 4.0.3, kernel 2.6.39.4, build number IML74K.US_epad-9.2.1.27-20120615. FWIW I keep it docked about 95% of the time, MobileDock version EP101-0213.
After installing the latest version of the Calendar app back in August, the app started to freeze up without the standard "wait/kill/report" dialog box. I could switch to the home screen but all I would see was the background image. No icons. Swiping moves the image, but doesn't change screens. I can still switch between running apps but the one that froze is useless. Reboot to fix.
Fast forward to last week when it started happening from within another (just-updated) app. Once, I could still see icons on the home screen, but they didn't move when I swiped the background image.
The developer of the second app suggested that I might have bad blocks in the internal memory or SD card. My SD card slot still has the dummy card in it, so that's not it.
According to Settings->Internal Storage, my internal memory is only about 50% full. (12.63G, 4.38 of which is apps).
Can someone please point me towards any utility apps that would help me diagnose the problem? (Have you seen it yourself?) I have experience with Linux tools but although I've rooted my TF101, I haven't needed to do anything but enjoy it as a consumer so far
I'm comfortable with a command line and can use ADB but I'm not sure where to start -- haven't hit on the right search terms yet, maybe.
Thanks,
C
Related
I'm becoming increasingly disenchanted with this thing day by day. I love the dual core, 512MB ram, wifi n and especially the 1080p capability, but is it worth the trouble? I begin to wonder...
Anyway, this just started happening recently to a point where it's become increasingly frustrating. I'm not sure if the enhancement pack or something else is the cause - I don't think it's the hardware unless it's going bad with time (hopefully not the case!). I haven't pinpoint anything, all I can say is that the last thing I did install was the enh. pack and that otherwise it's just stock 3389 on there.
My screen is becoming less and less responsive. Parts of it, are now taking a few touches to activate. The reason I don't think it's the screen itself or hardware is that after a while it seems fine - but after a fresh startup it's hell to do anything on there and it's not because of starting processes etc. because if I turn the screen to portrait mode I can touch the places I need activated and they'll work.
A definite area of contention for me, for example is the battery and wifi indicator which are, on first/fresh boot impossible to activate now. It takes a good 5 minutes of touching the screen all over the place to get it to a point where I can actually bring up the bubble dialogs from those 2 icons OR if I turn it to portrait mode, it will work.
I don't remember the screen ever being like this from fresh stock (3389) or even stock + gapps so I'm wondering if there's something in the enh pack interfering with touch driver performance or if there are new touch drivers in there that aren't as good as the old ones. The enh pack def. makes the pad feel quicker and I like the new Gmarket in there so now I have to decide between a faster/quicker but somewhat unresponsive device or an average speed device which is more responsive off the bat. Then there's of course the other possibility which is that it's not the software at all, but that the hardware really is finicky...in which case nothing would really make it work as it should. Oy veh.
Neoprimal said:
I'm becoming increasingly disenchanted with this thing day by day. I love the dual core, 512MB ram, wifi n and especially the 1080p capability, but is it worth the trouble? I begin to wonder...
Anyway, this just started happening recently to a point where it's become increasingly frustrating. I'm not sure if the enhancement pack or something else is the cause - I don't think it's the hardware unless it's going bad with time (hopefully not the case!). I haven't pinpoint anything, all I can say is that the last thing I did install was the enh. pack and that otherwise it's just stock 3389 on there.
My screen is becoming less and less responsive. Parts of it, are now taking a few touches to activate. The reason I don't think it's the screen itself or hardware is that after a while it seems fine - but after a fresh startup it's hell to do anything on there and it's not because of starting processes etc. because if I turn the screen to portrait mode I can touch the places I need activated and they'll work.
A definite area of contention for me, for example is the battery and wifi indicator which are, on first/fresh boot impossible to activate now. It takes a good 5 minutes of touching the screen all over the place to get it to a point where I can actually bring up the bubble dialogs from those 2 icons OR if I turn it to portrait mode, it will work.
I don't remember the screen ever being like this from fresh stock (3389) or even stock + gapps so I'm wondering if there's something in the enh pack interfering with touch driver performance or if there are new touch drivers in there that aren't as good as the old ones. The enh pack def. makes the pad feel quicker and I like the new Gmarket in there so now I have to decide between a faster/quicker but somewhat unresponsive device or an average speed device which is more responsive off the bat. Then there's of course the other possibility which is that it's not the software at all, but that the hardware really is finicky...in which case nothing would really make it work as it should. Oy veh.
Click to expand...
Click to collapse
Yeah, lots of us have had touch screen sensitivity issues. Luckily we figured out how to fix them. It's very simple.
If you are running the latest TNT Lite or Vegan ROM beta 4, the fix is very simple - drop an empty text file called "calibration.ini" in your /sdcard directory (you can copy it over from your desktop via USB cable, or just use ES File Explorer or similar file manager with create capability to create the file) and reboot, and *DON'T* touch the screen while your G Tab is rebooting. Voila, re-calibrated touchscreen, very sensitive again. Once it's working well, just delete that calibration.ini file so it doesn't recalibrate on every boot.
On earlier versions of the ROMs or on the stock 3389 ROM, the calibration executable looked for calibration.ini in the /sdcard2 directory so you needed an external microSD card to calibrate your touchscreen.
There's a whole thread on this called "touch screen sensitivity" or something like that where we figured all this stuff out originally.
rcgabriel said:
Yeah, lots of us have had touch screen sensitivity issues. Luckily we figured out how to fix them. It's very simple.
If you are running the latest TNT Lite or Vegan ROM beta 4, the fix is very simple - drop an empty text file called "calibration.ini" in your /sdcard directory (you can copy it over from your desktop via USB cable, or just use ES File Explorer or similar file manager with create capability to create the file) and reboot, and *DON'T* touch the screen while your G Tab is rebooting. Voila, re-calibrated touchscreen, very sensitive again. Once it's working well, just delete that calibration.ini file so it doesn't recalibrate on every boot.
On earlier versions of the ROMs or on the stock 3389 ROM, the calibration executable looked for calibration.ini in the /sdcard2 directory so you needed an external microSD card to calibrate your touchscreen.
There's a whole thread on this called "touch screen sensitivity" or something like that where we figured all this stuff out originally.
Click to expand...
Click to collapse
I already tried that and it had 0 effect. First I tried it in the original root, then I tried it on my actual SD card root. No effect whatsoever as to the accuracy or sensitivity of the screen. That is why I bothered to make this post at all.
In fact, I think I even made a post in a thread mentioning calibration.ini a few days ago. It def. does not work for me.
Neoprimal said:
I already tried that and it had 0 effect. First I tried it in the original root, then I tried it on my actual SD card root. No effect whatsoever as to the accuracy or sensitivity of the screen. That is why I bothered to make this post at all.
In fact, I think I even made a post in a thread mentioning calibration.ini a few days ago. It def. does not work for me.
Click to expand...
Click to collapse
Hmmm, that's weird. Okay, let me step you through running a manual calibration:
1) Create calibration.ini in the /sdcard directory (as described above)
2) Install "Android Terminal Emulator" from Market if you haven't already (it's free)
3) Run Terminal Emulator. Press menu button then Toggle Soft Keyboard to get the keyboard up.
4) type "/system/bin/TSCalibration" into the terminal and press enter
Let us know what output you see (if it's looking in /sdcard2 for calibration.ini instead it will tell you, if there's an error it will tell you, etc.).
/sdcard2
I think the post said you tried /sdcard and that won't work. You need a microSD crd inserted as /sdcard2 to do the fix and it doesn't work on the /sdcard that comes with the device.
justauser said:
I think the post said you tried /sdcard and that won't work. You need a microSD crd inserted as /sdcard2 to do the fix and it doesn't work on the /sdcard that comes with the device.
Click to expand...
Click to collapse
The enhancement pack includes the TSCalibration that works off of /sdcard, not /sdcard2.
"First I tried it in the original root, then I tried it on my actual SD card root."
Original root = internal storage/sd card, SD card root = sd card root, lol...as in little chip you stick into the phone or sd card 2.
I mentioned I tried both. I will attempt what rcg recommends and let you know.
Update: I got terminal emulator by zta labs (the only one I see in the android market as somehow it broke itself) and all that app does is force close.
Update 2: I got frustrated and just wiped it all and went back to 3899. Fixed now. Thanks all for attempting to help. Think I'm going to suck it up and stick with stock until 2.3 or Honeycomb comes.
I am a new user of touchscreen and android phones, so I'm not sure if I'm just being picky with my issues, or if they can be fixed. But if anyone can help I'd really appreciate it.
1. My phone will randomly mute mid-conversation. I then have to re-enter my password and get back to the phone "app" to un-mute it.
2. When I'm using the camera, if I leave it long enough for the phone to go into sleep mode I can't get it to turn back on. The touch buttons are still highlighted at the bottom of the phone, but the screen is black. I can hear the phone beeping like it is turning back on, but get nothing on the display. I then have to take out the battery, wait for 30-60 sec and then put it back in. Sometimes I have to do this repeatedly before it will start working again.
3. When I try to update the OS in Settings I keep getting the message that the phone cannot connect to the server. However, I have not other problems connecting to any other sites.
4. I added the facebook app and want to remove it now. I have gone into settings > applications and "uninstalled" it. However, the icon is still on my homepage and I can't seem to remove it. When I hold my finger on it a trash bin shows up below. But this only moves it to my apps page.
5. The phone is freezes pretty often. At least a couple times a day.
Ok, this is it for now. If anyone can help I'd really appreciate.
Thanks
I going to guess your still on 2.1 when was 2.1 stock the was way too touchy. The light goes out and you can't get to turn on unless battery pull this a issue found on 2.1 their a 2.2 update coming in late July. Update this on all this option will not work xt720 it not ota compatible so your settings area will not work . Be patient wait for Cincinnati bell update and if your not with them I intend to leak it.
Sent from my XT720 using XDA Premium App
As much as I'm liking my return to 2.1, it does indeed freeze up often, as I recall it did when I first got the phone. (the whole screen goes black, lights on bottom turn on thing)
Facebook app is a stock app and can't be removed unless your rooted.
Never had the mute issue.
The cannot connect to server thing I have had. But it's irrelevant as there shouldn't be any updates to get anyways.
Is updating the OS the best way to improve the performace of my phone? or should I still do the overclocking. If you advise to do the overclocking, should I wait untill I update the OS, or do it now?
There is no update to the OS, except for one that just overclocks from 550 to 720mhz. Chances are you already have that though. I do think that overclocking is a good idea if you want to increase the speed of your phone obviously. 1Ghz is nice and stable.
EDIT: Or do you mean update as in install one of the 2.2 ROMs from here?
I think Queenmantis's problem are related to the original Home app. try some Launcher apps such as Launcher Pro.
for now, my favorite is GoLauncher EX, with the latest update last week, that app totally rock. you guys should try.
I really love Dexter's 2.2, but the short battery life keeps bugging me so I've already went back to 2.1 since last week. I've got no modification except Milestone Overclock + App2Card 2.8.2. Eclair is still so sweet.
Hi I have bluesteel I have modified it some and would put up against any of 2.2 or 2.1 my numbers. Startup 65 memory and regular memory is 70 to 88 program memory and don't freeze and no lag.
Sent from my XT720 using XDA Premium App
Wait for CBW's update if you don't want to root.. If you're open to the idea of rooting your phone, then go ahead and update to Dexter's 2.2, save yourself the headache, then flash one of Khalpowers' ROMs, that should fix you up real good, there's always the option of going back to stock of you don't like the results, or go back to the "official 2.2" from CBW once it's available. But that's just me..
Queenmantis said:
I am a new user of touchscreen and android phones, so I'm not sure if I'm just being picky with my issues, or if they can be fixed. But if anyone can help I'd really appreciate it.
1. My phone will randomly mute mid-conversation. I then have to re-enter my password and get back to the phone "app" to un-mute it.
2. When I'm using the camera, if I leave it long enough for the phone to go into sleep mode I can't get it to turn back on. The touch buttons are still highlighted at the bottom of the phone, but the screen is black. I can hear the phone beeping like it is turning back on, but get nothing on the display. I then have to take out the battery, wait for 30-60 sec and then put it back in. Sometimes I have to do this repeatedly before it will start working again.
3. When I try to update the OS in Settings I keep getting the message that the phone cannot connect to the server. However, I have not other problems connecting to any other sites.
4. I added the facebook app and want to remove it now. I have gone into settings > applications and "uninstalled" it. However, the icon is still on my homepage and I can't seem to remove it. When I hold my finger on it a trash bin shows up below. But this only moves it to my apps page.
5. The phone is freezes pretty often. At least a couple times a day.
Ok, this is it for now. If anyone can help I'd really appreciate.
Thanks
Click to expand...
Click to collapse
1. Maybe the Proximity sensor for auto turn-off has problems, when you are using the phone, the backlight turn-on and your face or your ear touch the surface and it mute.
2. Obviously this is a hardware problem, you should bring your phone to where you buy it to check.
3. I have the same problem, but I think this is not our phones' fault. Motorola seems not to support this phone anymore.
4. Facebook is considered to be a system app on this phone, you can not remove it. The app call facebook you installed on the phone, just the update of the original facebook app. Don't worry about that.
5. This maybe is relevant with the problem you have in the number 2 - a hardware problem.
-------------------------------------------------------------
Please forgive if there is something wrong above. I'm willing to listen and learn.
thank you
spiderx_mm said:
I think Queenmantis's problem are related to the original Home app. try some Launcher apps such as Launcher Pro.
for now, my favorite is GoLauncher EX, with the latest update last week, that app totally rock. you guys should try.
I really love Dexter's 2.2, but the short battery life keeps bugging me so I've already went back to 2.1 since last week. I've got no modification except Milestone Overclock + App2Card 2.8.2. Eclair is still so sweet.
Click to expand...
Click to collapse
May you show me how to install App2Card 2.8.2 on Eclair. I try but i failed. What should I know first to do this.
Any news on how you did..?
Sent from my XT720 using XDA App
CrystalShield said:
May you show me how to install App2Card 2.8.2 on Eclair. I try but i failed. What should I know first to do this.
Click to expand...
Click to collapse
I think most important part of App2Card is partitioning of SD card. I had tried the partitioning tool in App2Card but it never fail to fail . So I partitioned my card as below and I use "Parted" software inside Ubuntu. My SD card is Sandisk 8GB SDHC Class6 card.
1st Partition - FAT32 (7.2 GB)
2nd Partition - EXT3 (512 Mb)
3rd Partition - SWAP (256 Mb)
Create one partition at a time. Don't create everything in one batch.
Then, the card should be ready to use.
now come with the App2Card. Open the app, make sure u grant root access and all, make sure the app detect the card. then close it again. (that might be the trick). And open it again. Just do open and close till the "What's New" pop-up never show up. It might be two or three times. Then click "Install EXT/Transfer apps to EXT" button.
it will install, make the phone reboot and configure.
after the phone is rebooted, open the App2Card to make sure it show no error message. If there's any error message, just try to reboot the phone. It will surely work.
I'm not rooted and in the five months I've had the 4G Slide I've never had any force close issues.
This week I moved all the apps that could be moved from the phone to the SD card, and ever since I've had constant force close issues, either of the apps themselves or the genius button or the whole system. Generally it happens every time the phone is rebooted but can also happen at any random point. It will methodically go through each app alphabetically with the same 'force close' message and asking me if i'd like to report it to HTC.
I was wondering if anyone else had experienced this issue and was also wondering if there would a logical explanation as to why transferring the apps to the SD card might make the phone unstable.
well rule #1 that i've learned is that never move any app that has a widget or any kind of notifications. even if you're not using the app's widget or notifications. it just seems to mess stuff up.
and then this one i found out on my own: moving stuff to the sd card is exactly when problems start haha. it sucks. probably the biggest problem with android as an operating system. i don't know why they even give us the option, because it almost always causes trouble.
BUT if you stick to only moving games (and games that have no kind of notification systems... so don't do words with friends, for example), then you should be good.
Hi devvers,
The last update for the German version of the tablet is not working so well for me.
First things first: the tablet drains a lot of battery power! Have you noticed that too??
And second: when the tablet is almost empty like 7%, the tablet turns off instantly. I don't see the second warning screen because there's still over 4% left. It used to show me the second screen and then when it's really empty, Android powers off.
Turning the tablet back on isn't an option anymore. You have to plug the charger and then it'll boot again.
I'm using a stock rom and no root whatsoever.
Am I the only one out there? :/
Ps. Are there people having a notification showing that the sd card is inserted every hour or so?
Okay, this problem has occured multiple times and today nothing happend and everything went how it should. Awesome.
TomONeill said:
Okay, this problem has occured multiple times and today nothing happend and everything went how it should. Awesome.
Click to expand...
Click to collapse
Self-Healing
With battery drains though, it's better to check your Applications and see if you downloaded some apps that might be using too much battery. Go to Settings/Apps and select Apps running. This will show you what's running in memory.
MD
Thanks for your reply.
Yeah, it's self-healing xD
I did last week and I didn't notice any particular app eating too much RAM memory. I also checked the cached processes, but that wasn't a problem either. I did turn off some notifications from games I didn't play anyway, but that did not really help.
May I ask how much RAM you have left when having nothing running?
I have between 200-300 MB left, sometimes after a boot 300 to 400, but not really that often.
I'm running the stock ROM by the way.
Another thing: Do you have a SD card in your SD card slot? Cause every now and then since the JB update I get the notification "SD Card is inserted". Which I'm sliding away and it pops up back after having my tablet in stand-by modus for a few minutes (perhaps hours).
Edit:
I have to say that I have been installing a lot of apps, but that I deleted a lot of them 2 weeks back. Then I checked my sdcard data (internal data) for any traces of deleted apps, but I was quite surprised how little there was left of traces of deleted apps. Microsoft could learn from that (though it's not Microsoft who makes their uninstallers not fully deleting everything. But am going off topic now.). Could that may have effects on the RAM? I don't assume it will, but just FYI.
First of all, thanks to chui101 and all the other people here who put in the effort to get CyanogenMod to run on this phone. However, I'm having a bit of a problem with my phone slowing down severely and becoming unresponsive, usually at the lock screen. The specific issue is that the lock screen will be on screen, but not respond to button presses, or respond very slowly, and then it will do the "old CRT television turning off" effect much much slower than it's supposed to (think close to a minute), go blank for a while, the lock screen comes back up, another very slow screen turn off effect, and the whole process keeps repeating until I get tired of it and pull the battery to reboot the phone. This issue happens to me with both the 2012-11-21 and 2012-11-25 nightlies. To me, the behavior sort of seems like an out of memory issue, maybe some program is leaking memory or something.
Things that cause the freezing issue:
Power button presses too close together
2 cases of a call coming in while the phone is locked and playing music in Apollo
Things I've tried thus far:
Switch launcher from Trebuchet to NovaLauncher
Set Background Process Limit from "Standard Limit" to "At most 3 processes"
Set "Force GPU rendering"
Remove SD card
Out of those, pulling the SD card is the only one that seemed to help. The SD card I had installed was a 16GB SanDisk Class 2 card with ~3.7 GB of music along with less than 10MB of small text files, ring tones in .wav format, pictures, etc.
I put the 2GB card that originally came in the phone back in, this card currently has nothing but the text files and ringtones and a few pictures.
Is anyone else getting hit with this problem? What can I do to help? I don't know much about android ROM development, but I can handle collecting a LogCat from a case where the problem I'm describing is happening and know a reasonable amount about general Linux stuff, just not Android internals.
Thanks!
I used to own an LG Mytouch Q, the only reason I'm even remotely interested in this thread.
However, you should definitely post in that specific thread, as it's basically the only group of Mytouch owners and they should give you lots more help
Sent from my DROID2 using xda premium
I would, but I just joined here so I can't post in the dev forums. I'm hoping someone there will see this post.
Update
With the smaller SD card without all the music files installed, I'm getting less of the freezing problem, although I am not certain whether this is due to the music files not being there, or me not using the phone to play music. I guess the next part of this experiment is to go back to the card with the music files on it but not play any of them. I did grab a LogCat from one of the cases where the phone is 'freezing' and see a bunch of "Application Not Responding" messages, and the CPU usage stats that follow these messages indicate that most of the CPU time is being used by 'iowait,' for instance "100% TOTAL: 0.3% user + 6.9% kernel + 92% iowait". I've read some threads relating to other phones indicating that this could be some process poking around somewhere in storage. I'm thinking that running top from adb shell next time the phone ends up in this state might give some clue as to what's eating the CPU.
Also, I've hit the issue with email message bodies showing up blank that others on this phone, and on CM9 on the non-keyboard LG Mytouch (E739) have experienced.
Hope I'm not spamming with yet another status update, but I tried disabling live wallpapers (going instead to no wallpaper/black screen) last night, and I haven't had any of the freezing problems today. I'll try adding the music files back and see if the problems return then.
* Update 11/29/2012
I put the 16GB card with ~4GB of music back in the phone, used it all day at work for listening to music/checking email/some web browsing without any crashes. (Still with live wallpaper disabled) So, I'm starting to think live wallpapers are causing my problem.