Database Info

Trouble with Touch screen, multi touch

I have cyanogens latest rom installed. I tried all the previous versions as well and I keep
having the same problem.
My Touch screen on my MyTouch3g keeps, for lack of a better description, going to sleep. I can still use the multi touch zoom function in the browser,but I cannot screen flick or get the icons to respond. I can hold the bottom of the screen and turn off and on and sometimes this will repair the problem. It seems to recur randomly. Is there any place to look in the log file to see what is causing this? I'm at a total loss after 6 or so roms and still no go. I tried the stripped down rom labeled TMO-OTA-US-DRC83-Rooted_update and also the expansion pack to no avail. I can't really believe this is hardware related since it's random and fixes with a power cycle most times. I'm just finding it annoying as hell, and I hope someone might be able to point me in the right direction.
I've done the bootloader flash/delete data and re-installed each time.
Latest rom from Cyanogen isCyanogen mod 4.2.4
Kernel version is 2.6.29.6-cm42 (does this matter? I include because I'm not sure)
Thanks
Mike

Maybe this will help
look for a post on how to install cyanogen rom on your MTY3 and dowlaod the rooted rom there.
secondly,
see this thread and the last post from me.
http://forum.xda-developers.com/showthread.php?t=583683

I've done multiple re-installs. The same problem keeps resurfacing within minutes.
I can use the touch screen and then it craps out. Oddly it will many times still allow pinch and zoom multi-touch in the browser. But single touch, such as in typing web addresses etc. , does not work.
Does anyone have an idea as to why this might be happening? Is there a particular file that is escaping the wipe/ reboot and reload process that is still not being replaced.
I'm curious if the Kernel has anything to do with this.
Any ideas?
Mike.

try redownloading the rom and the htc image like redownloading from the source wipe the ext erior partition as well pretty much completely restart the process except keep root lol... if that doesnt work then you need to unroot and reroot the bad boy all a learning experiance

Wipe the exterior partition? Doesn't this occur when I do a wipe/data? I have never partitioned the sd card. It has been the same since I received it. Will this affect the screen behavior?
Thanks for the input
Mike

oh well I figured you would be running apps2sd which requires a exterior partition or ext2/3/4 as some may call it... most roms require a wipe of that as some storage will transfer to there and cause problems ona seperate rom for some but if yours is a fresh sdcard then the only thing I can suggest is get a redownload of the cyan rom

Any new(er) touchpad drivers/sw?

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.

[Q] TnT Lite 4.3 impressions

I've just moved from VEGAn 5.1.1 to TnT Lite 4.3
Quadrant scores didn't change, but overall the mod feels more responsive.
Video playback improved a lot. Now I can watch x264 movies without converting them from *.mkv with hardware acceleration, which didn't work fast enough on VEGAn.
There is one issue:
- I was getting FC before I formated data partition, but after that Home button doesn't work. I remember I had the same issue on GingerVEGAn and solved it somehow... Any hint?
Thanks roebeet for the excellent mod! Kudos to gojimi, I used VEGAn for over a month.

ivan.volosyuk said:
I've just moved from VEGAn 5.1.1 to TnT Lite 4.3
Quadrant scores didn't change, but overall the mod feels more responsive.
Video playback improved a lot. Now I can watch x264 movies without converting them from *.mkv with hardware acceleration, which didn't work fast enough on VEGAn.
There is one issue:
- I was getting FC before I formated data partition, but after that Home button doesn't work. I remember I had the same issue on GingerVEGAn and solved it somehow... Any hint?
Thanks roebeet for the excellent mod! Kudos to gojimi, I used VEGAn for over a month.
Click to expand...
Click to collapse
I had that exact same problem during testing - I thought it was my imagination because I reflashed and it went away. So I thought it was a one-off.

roebeet said:
I had that exact same problem during testing - I thought it was my imagination because I reflashed and it went away. So I thought it was a one-off.
Click to expand...
Click to collapse
Did you clear userdata next time? It appeared after I erased userdata. What do you suggest?
Update: I cleaned up data/cache, re-installed TNT Lite 4.3, still hardware Home doesn't work. Usually it means that SetupWizard wasn't ran, which is true in my case. Is it supposed to run?

ivan.volosyuk said:
Did you clear userdata next time? It appeared after I erased userdata. What do you suggest?
Update: I cleaned up data/cache, re-installed TNT Lite 4.3, still hardware Home doesn't work. Usually it means that SetupWizard wasn't ran, which is true in my case. Is it supposed to run?
Click to expand...
Click to collapse
No, I pulled it out in this release (it doesn't even pop up). I will do some more tests today. I remember re-flashing (not re-wiping) and it went away, but let me do some more tests.
TwoTapsX does not have the issue, but maybe there's something in that init.rc that I need (the system image between the two is the same). If it's the init.rc, I might have to make a 4.4.0 to fix it, just keep that in mind. I'll figure it out , and apologies.

ivan.volosyuk said:
Did you clear userdata next time? It appeared after I erased userdata. What do you suggest?
Update: I cleaned up data/cache, re-installed TNT Lite 4.3, still hardware Home doesn't work. Usually it means that SetupWizard wasn't ran, which is true in my case. Is it supposed to run?
Click to expand...
Click to collapse
is it just the hardware home button that doesnt work? or does the one built into the software not work as well?

I found root cause
Updated on the TNT Lite thread, as well - I'll have a supplement up this evening. It was actually the SetupWizard.apk, believe it or not. I wasn't looking there at first as it made no sense why it would cause a problem (it's for Gapps), but sure enough it's needed.

Issues with TNT 4.3
I can't get the GTAB to wake from sleep since I went to 4.3 and when I installed 4.3.1. If the GTAB is left sleeping then I have to reboot it or when I put it to sleep with the power button. Is anyone else having this issue. Did something change so if it is sleep for a while you can't wake it up? Also my battery is draining because the android system is running at 78%, has anyone else noticed that?

KJRain said:
I can't get the GTAB to wake from sleep since I went to 4.3 and when I installed 4.3.1. If the GTAB is left sleeping then I have to reboot it or when I put it to sleep with the power button. Is anyone else having this issue. Did something change so if it is sleep for a while you can't wake it up? Also my battery is draining because the android system is running at 78%, has anyone else noticed that?
Click to expand...
Click to collapse
It could be the mix of 3588 kernel and 3991 system (not playing nice?). This was what I was going to release before I went to TNT Lite 5, and that did not go over well.
Battery drain should be the same, but long-term tests were not that extensive.

roebeet said:
It could be the mix of 3588 kernel and 3991 system (not playing nice?). This was what I was going to release before I went to TNT Lite 5, and that did not go over well.
Battery drain should be the same, but long-term tests were not that extensive.
Click to expand...
Click to collapse
Also, I just wanted to let you know that I really like the TNT lite rom and everything that you are doing to make as efficient as possible.
Thanks.

roebeet said:
It could be the mix of 3588 kernel and 3991 system (not playing nice?). This was what I was going to release before I went to TNT Lite 5, and that did not go over well.
Battery drain should be the same, but long-term tests were not that extensive.
Click to expand...
Click to collapse
Would you suggest a nvflash, update to 3991 then going to 4.3?

KJRain said:
Would you suggest a nvflash, update to 3991 then going to 4.3?
Click to expand...
Click to collapse
That's a bit of a roundabout way, and a bit risky with 3991. If you want the "cleanest" setup possible, then I would do this:
1) nvflash to 1105 bekit.
2) update to 3588 stock, either via an OTA update or a manual install
3) Wipe the user data
4) Then install your mod of choice.
Optionally, install clockworkworkmod and do an SD re-partition (and then remove it). I've had to do this a few times to clean up some issues, but then again I flash my system a LOT so my setup is different than most.

KJRain said:
I can't get the GTAB to wake from sleep since I went to 4.3 and when I installed 4.3.1. If the GTAB is left sleeping then I have to reboot it or when I put it to sleep with the power button. Is anyone else having this issue. Did something change so if it is sleep for a while you can't wake it up? Also my battery is draining because the android system is running at 78%, has anyone else noticed that?
Click to expand...
Click to collapse
I don't have wake hang up issues so far. I installed custom kernel (ClemsynFroyoVer6.zip) right after I flashed 4.3.1 supplementary and cleaned up data again. The kernel supposedly fixes this kind of problems.
http://forum.xda-developers.com/showthread.php?t=895825
4.3.1 fixed the Home button issue, so now I'm pretty happy with the result.
KJRain said:
Would you suggest a nvflash, update to 3991 then going to 4.3?
Click to expand...
Click to collapse
I didn't do that it works fine for me. I came directly from VEGAn 5.1.1.
Custom keyboards is tricky with the TNT Lite, but possible. Lock screen with pattern also a little bit tricky.
I use Titanium Backup to keep my apps during wipes, so I can go easily between different mods, I just restore only missing apps + data and don't touch system.

[Q] Problem: Screen doesn't show anything after some time

I have a problem with my Xt720.
I have the Froyo Rom by khalpowers V3. (this one http://forum.xda-developers.com/showthread.php?t=1002993)
Everything works just fine and how it should. But after about 20 minutes when my screen turns off or when I turn my screen off, I can't turn it on again.
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
I'm not sure but I think the touch screen doesn't work either because I can't unlock it by sliding the unlock thing. (or I just can't find it when the screen is off)
This began today and I did nothing extraordinary with my phone. When it started I had the Dexter's Froyo (http://forum.xda-developers.com/showthread.php?t=939644) Version 1.2. But it has never been a problem before.
Then I flashed the above called Rom by khalpowers and it's still the same problem.
Everytime it happens I have to remove the battery and reboot the phone to use it again. This is very annoying and not how it should behave.
Wat do?

Monthana said:
I have a problem with my Xt720.
I have the Froyo Rom by khalpowers V3. (this one http://forum.xda-developers.com/showthread.php?t=1002993)
Everything works just fine and how it should. But after about 20 minutes when my screen turns off or when I turn my screen off, I can't turn it on again.
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
I'm not sure but I think the touch screen doesn't work either because I can't unlock it by sliding the unlock thing. (or I just can't find it when the screen is off)
This began today and I did nothing extraordinary with my phone. When it started I had the Dexter's Froyo (http://forum.xda-developers.com/showthread.php?t=939644) Version 1.2. But it has never been a problem before.
Then I flashed the above called Rom by khalpowers and it's still the same problem.
Everytime it happens I have to remove the battery and reboot the phone to use it again. This is very annoying and not how it should behave.
Wat do?
Click to expand...
Click to collapse
Let it charge for a while and try again. Your battery may be extremely low. Turning on the button lights is one thing it does when there isn't enough power to boot even to the "display a charging battery" mode. This has happened to me.

I've had this issue ever since I got my phone. This would just happen completely randomly (nothing to do with battery or anything else). It happened pretty unfrequently and barely ever happens ever since I put on Dexter's 1.3. Not sure what causes it - but it looked to be completely random for me.

Monthana said:
I have a problem with my Xt720.
I have the Froyo Rom by khalpowers V3. (this one http://forum.xda-developers.com/showthread.php?t=1002993)
Everything works just fine and how it should. But after about 20 minutes when my screen turns off or when I turn my screen off, I can't turn it on again.
I press the Powerbutton and all that happens is that the led row lights up but the screen stays black.
I'm not sure but I think the touch screen doesn't work either because I can't unlock it by sliding the unlock thing. (or I just can't find it when the screen is off)
This began today and I did nothing extraordinary with my phone. When it started I had the Dexter's Froyo (http://forum.xda-developers.com/showthread.php?t=939644) Version 1.2. But it has never been a problem before.
Then I flashed the above called Rom by khalpowers and it's still the same problem.
Everytime it happens I have to remove the battery and reboot the phone to use it again. This is very annoying and not how it should behave.
Wat do?
Click to expand...
Click to collapse
Another suggestion. Since you've already swapped ROMs, maybe it's related to the SD card. Perhaps try backing your SD card up, reformatting it and copying the data back (do this on the PC not through USB access). Then reinstall your rom in OpenRecovery and factory wipe.
(You don't happen to be running WidgetLocker?)

@Mioze: The battery was at 70% a few hours after I loaded it to 100%, so that's probably not the problem. I don't have widgetlocker and it also happened with the sd card taken out.
But it didn't happen since I've started this thread so maybe I'm lucky and syrenz was right.

i have had this problem on every rom. it is related to sdcard. happens to me almost everytime i try to unrar one of khals rar files it always happens when im doing something sdcard related. last time it happened i did a battery pull and when it powered up my sdcard would stop checking for errors and everytime the screen turned off it wouldnt come back up. i had to plug into pc and check for errors and then it worked again without having to reformat it. my advice is get a faster sdcard. the stock one just doesnt cut it.

Trying a 4Gb Kingston Sd card now I used with my Dslr before.
I used the stock sd the whole day after I checked it for errors yesterday and it went well until I tried to download something from the store.
By now there seems to be no problem. Going to update my post if the problem still exists.
If it's ok: Thank you all for your efforts to help me.

Now this is ironic, as my phone began doing this today after put a new 32GB class 10 (Patriot) microsdhc card and reflashed Dexter's 1.3 and added bugfix v3 to it. After some tinkering, I think I nailed it down to me undervolting the processor.
I'm assuming the new microsdhc card need's a little more power than I was allowing. I was clocking the processor to 720Mhz/Vsel43, I left the speed at 720Mhz, but increased the vsel to 45, which seems to have solved the above described problem. However when I tried to copy my music over to the phone, it borked out again. So I've increased the vsel to 50 and things seem to have settled down. (fingers crossed)
G.
Ack! I spoke too soon. I just tried to install Steve Lin's Gingerbread keyboard and the phone reboots at the end of the download, even though I tried increasing the vsel. Going try clearing the Dalvik/Cache and see if that helps any.

I've flashed my XT720 to the khalpowers MIUI-Optimized V3 with the camera update.
I originally had a Sandisk 8GB Class 4 SD card, but after installing a new Adata 8GB Class 6 SD card, I started having the same issues. I was running Milestone Overclock on non-custom overclock settings, so it was running at 1GHz @ 74 vsel.
Honestly, I don't know that I've seen a discernible difference between the Class 4 and Class 6 card, so I may go back to the original card until I get more concrete data on how to fix this.

Let me share my 2 cents regarding sd cards.
first trouble shouting:
1. use the phone without the sdcard to see if the problem disapear
2. while doing 1. test the sdcard. Have in mind that sdcards are little bit different from normal hdd. For example i had 2 sdcards which locks the phone, but seems good on normal fs checking (even bad sector check option forced). but this 2 cards failed on the following test
test read speed of the sdcard for every 100 MB of it. for my desktop the script looks like:
Code:
i=0; while [ $i -lt 75 ]; do echo $i; dd if=/dev/mmcblk0 of=/dev/null bs=1M count=100 skip=`expr $i \* 100`; i=`expr $i + 1`; done
dd utility will probably report the speed (else just type time dd ....., then you will have the time)
if the card is good, then the speed has to be almost constant
for example on the good card i am using now is almost constant from 13.1 till 13.6 MB/s
for one of the bad, i observerd droping from 10 MB/s to 3 MB/s for a specific space range. then had run several tests just in this range and it turnout that this area of the sdcard is slow. That means that the card is on it way to the RIP.
For us it means that some sdcard io will timeout and soft lookup can happen (e.g. so called warm reboot, or just system_server kill by the watchdog). The other possibilities is more worse, just freeze and the watchdog cannot kill the system_server (probably because hang io operation)
Personally i was runing adb shell when the phone had freeze. it turns out that the linux works somewhat, but even as root i was unable to kill any process (probably because io hung operation), also every operation with the sdcard has hangt the current adb session, so i have to open new one....
secondly performance
0. If you wish you can perform the read speed test from above, but with write and to observe weak areas of the new sdcard
1. align the partitions on 8192s boundary (both of them to start on 8192*X sector)
2. format the fat32 so 64k logical cluster is formed (i use mkfs.vfat -S 4096 -s 16 options )
3. do the read_ahead tweak
4. be sure to using noatime mount options
5. vold checks the fat partition for you, make sure that thex ext[234] partition is checked before is mounted
6. If you decide to move the /data/dalvik-cache, move it to the /cache partition, not the ext[234] one
and do not forget, that free internal phone storage has no benefits. so as the internal nand is faster, use it as much as you can
p.s. and just to share: i have troubles with the thumbnail service. it turns out that when it runs (e.g. when i lock the display) it find some broken images and crashed badly, invoking warm reboot. after deleting this broken images, this problem was solved

I've been using the Kingston 4gb sd for a few days now and the problem's gone.
So that might be the solution.

I use 8GB C2 sdcard, and turn off desktop cache in system setting of ADW, this problem was gone.
It seem to be caused by ADW places cache in SD.

I've left my Adata 8GB Class 6 SD card in for now, but after removing the SD Speed Boost app, it appears my problem has gone away. I've never had the persistent memory setting enabled on ADW, btw.
Edit: I was curious if the SD Speed Boost would work after a reinstall, but 20 minutes after, I was pulling my battery, so I'm pretty sure it was that app at fault.

easye420 said:
i have had this problem on every rom. it is related to sdcard. happens to me almost everytime i try to unrar one of khals rar files it always happens when im doing something sdcard related. last time it happened i did a battery pull and when it powered up my sdcard would stop checking for errors and everytime the screen turned off it wouldnt come back up. i had to plug into pc and check for errors and then it worked again without having to reformat it. my advice is get a faster sdcard. the stock one just doesnt cut it.
Click to expand...
Click to collapse
I got the issue even I'm using the class 10 SD card it seems not related the SD speed.

Annoying.......
This problem just started happening to me but I doubt that it is a SD card problem. Mostly since my phone has been unresponsive since yesterday afternoon and I can't even get the LEDs to light up or get the screen on at all. I got it to work after relentless battery pulls and taking the SD card and SIM out. But I decided to turn it off so I could pop the SD and SIM card back, it went back to its non-responsive mode. I also am unable to get to recovery mode or even the bootloader. My tech always seems to break all on the same day (my bike too >_<).

just try without sdcard
Sent from my Milestone XT720 using Tapatalk

I'm almost positive this is sdcard related it only happens to me when I'm doin something sdcard related. Happens like clock work when I try to unrar one of khal themes that's 100 or more megs same when I use the unyaff app to extract my data.img from my back up. Ive had this problem ever since upgrading to 2.2 never happened on 2.1 I've just gotten used to it. I dont think its gonna go away I'm thinking the sdcard must timeout or something.

easye420 said:
I'm almost positive this is sdcard related it only happens to me when I'm doin something sdcard related. Happens like clock work when I try to unrar one of khal themes that's 100 or more megs same when I use the unyaff app to extract my data.img from my back up. Ive had this problem ever since upgrading to 2.2 never happened on 2.1 I've just gotten used to it. I dont think its gonna go away I'm thinking the sdcard must timeout or something.
Click to expand...
Click to collapse
Well just did a battery pull again and just took out the SD card and put the battery back in and tried to turn it on again but to no avail. Really annoying not having having my phone.....

This is also happening to me too... regardless if i have anything installed or accessing any files on my SDcard... and i already flashed my xt720 back to stock... and still the same... already changed my SDcard from the 8gb that was included on the package to 16gb... but still the same... i am very dissapointed with this device... just got this last week...

Still Annoyed....
My problem is still persisting after 2 days now and I'm torn between junking this phone and getting something else or trying to find a way to get my phone back in working order. I've tried just about everything I can do physically with the phone (battery pulls, w/o SD or SIM or with both in or one or the other out, etc........). So far all I have right now is a $400 dollar paper weight.
On another note, for some reason it keeps phoning my dad or sending him text messages with random assortments of code or error messages..........

[Q] Multiple Issues with xt720

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.