Database Info

Odd problem

Not sure if anyone has had this problem but I'm seeing some really odd issues, sometimes the screen starts moving really quick almost like flickering but from left to right as if I'm holding finger on the screen and moving it extremely fast. Sometimes it seems like touch screen doesn't work until I hit power and menu right after, also randomly core apps would crash.
I'm on jf1.42 rc33.

are you using any themes? I've encountered similar problems, but only after flashing multiple themes without wiping. i've never had any problems after a fresh wipe and reflash of JF 1.1*.

tchort said:
Not sure if anyone has had this problem but I'm seeing some really odd issues, sometimes the screen starts moving really quick almost like flickering but from left to right as if I'm holding finger on the screen and moving it extremely fast. Sometimes it seems like touch screen doesn't work until I hit power and menu right after, also randomly core apps would crash.
I'm on jf1.42 rc33.
Click to expand...
Click to collapse
i'm having similar problems but wasn't sure if something i did screwed it up, i was getting random core apps crashing on 1.41 RC33 and to test a script i wrote and an app made by another i completely wiped every thing to where the phone wouldn't start at all, i achieved this with adb shell wipe all
i wouldn't suggest doing that unless you have an update.zip waiting to be flashed to your phone, i put the phone back to warrenty standards and then started EVERYTHING all over so i could test the things i wanted to. when i finished testing i rooted and put 1.42 on and it seemed a little better all day until it popped up and phone process, settings, and core all three crashed at the same time about 30 minutes ago. my flash was 100% clean as there was nothing on the phone at all including OS, i completely wiped the system partition and data and refused to flash my nandroid back up since i didn't want the same problems. i hope someone else knows what's going on and we can fix this

I went from stock rc 30, rooted, JF RC 30, Themes (many), RC 33,JF ADP 1.1, then back to RC 33.
I had an issue of contacts not syncing, and the import contacts from sim caused a core force close.
So i did a freash install of JF 1.43 RC33 and it worked again. No screen problems but I did have a few core apps force closing. It hasnt happened since my last install of RC 33. Im running a modified theme now, my own with very little changes.

jonnybueno said:
are you using any themes? I've encountered similar problems, but only after flashing multiple themes without wiping. i've never had any problems after a fresh wipe and reflash of JF 1.1*.
Click to expand...
Click to collapse
No themes, if I do a wipe, what happens with paid apps that I have installed does anyone know?

Looks like it was the related to multi touch, after doing another wipe and installing a build with out multi touch the problem went away no more rapid screen movement and apps are not crashing

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

[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..........

Experiencing Something Strange....

At the time I had Vegan Ginger Experimental running and the VT Launcher Beta. Everything was working just fine (or as fine as an exp. could run), then I thought to check Vegan-Tab's site http://vegantab.gojimi.com/2011/02/24/new-boot-animation/ just to see if any updates had been posted, and noticed a newer version of the VT Launcher (Beta 1.3) had been uploaded (or Im just an idiot and it was the same version) , so I decided to install the newer? version... this is where the strangeness incurs.
Instead of just installing the newer launcher over the one I had, for some reason I uninstalled the one I had then installed the other. Please note that at this time I had VT Launcher set as my default launcher (not sure if that would matter). After the install, I hit the Home button and all Hell broke out.
- It seemed like my touch capabilities (atleast on the screen, 4 side buttons still worked) just stopped working
- The window that pop ups from a long press on the Home page (wallpaper, shortcuts, etc..) kept popping up on its own, and everytime I would hit the Home side button (all I could do), the window would go away but would come back after bout a second... everytime.
Initially I thought no big deal, I made multiple backups for different ROMs and thought just re-flasing a ROM or using a backup to restore a previous ROM would fix the issue, no dice...
I tried:
- Re-flashing VTab Ginger Exp. (yes, with proper kernel)
- Flashing other ROMs (TnT 4.25, Vegan 5.1.1, even the Stock 3588)
- Restoring previous backups (all ROMs listed above)
- All the while changing the kernel used depending on the ROM (Ginger/Froyo)
- I used all the steps Ive read about in installing a ROM on each flash/restore
(Wipe Factory/Reset & Cache, Mount System/Data/Cache, Format S/D/C)
- Even tried clearing Delvik and resetting Battery Stats
Everything I tried resulted in the same symptoms:
- My Touch capabilities not working (or atleast ~98% not working, very strange)
- The long press on Home Screen window constantly popping up
I dont understand how uninstalling a default launcher and reinstalling the same launcher could cause this across multiple flashes/restores but that is when this began. I have the touch calibration zip used in cwm somewhere on my laptop and will be trying this next, just not sure if it will make any difference.
Sorry for the long post, just thought if I listed all the symptoms I observed, this would hopefully ring a bell for someone who experienced the same thing, or atleast would know what I could try next. Thanks for any help!!
Edit: I posted this in the Vegan Ginger thread, sorry for the double post but wasnt sure where it should go since my issue spans any ROM Ive tried (although it originated in Vegan Ginger). So available forum mod, do what you must. Thanks

Display / menus freezing and / or disappearing, system apps force closing

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.