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

HELP: Phone locks up and dies at random

I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!

Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.

TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?

Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...

1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps

I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...

TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.

Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.

[SOLVED] LGO3D randomly shuts off.

My newly bought shiny LGO3D phone has a habbit of randomly shutting itself down no matter what ROM / Firmware i have on it.
I've tried stock, king ROM, and a few others. all randomly shutdown. i wouldnt mind if it had rebooted by itself at least it would come back on but it just goes off!
i reach into my pocket -- lo and behold the phone is off!
I've read lots of Optimus2x threads about a similar issue ... some blame the android system and some blame the hardware.
i wonder why there isnt a log in the android system describing an error or whatever?
can anyone help?

maybe your battery is a bit loose?
go stick some strips of paper at the bottom edge of the battery to make sure its nudged tight.
not sure, maybe a possible solution

i think i may have solved this issue...
what i did was this:
install CWM and reboot into the CWM menu.
i deleted everything. cache, delve cache, battery stats, everything thats deletable i did it.
i am currently using king_rom (which was doing the same problem for me to start with) and i can say the phone has been running ok for about 2 days now.
keeping fingers crossed.

usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it

Blezz said:
usually cache + dalvic + battery states are deleted on every rom flash
if it appears again pull out your sdcard
fixed all reboot issues for me... wonderful to have a phone able to play 3d + record 3d/1080p and cant use a sdcard
hoping the 2.3 update will fix it
Click to expand...
Click to collapse
i never sacrificed the sdcard though its in there and its working fine.

to stop Verizon from forcing update

to stop Verizon from forcing update
Use Titanium to freeze com.smithmico
i lost root because vz forced the update so i reinstalled .5 oem then used revoluton to unlock boot in stall SU installed .9 radio seems to work well rebboted it pop saying .9 would start download in 26 secs i stoped it from installing
i remembered reading about smithmicro and OTA so i froze it so far n more pushed OTA ...
your mielage may vary

Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.

Could you tell me exactly how you reinstalled .5 after having .9 already on the phone?

http://www.multiupload.com/WES9PABEQF
rename it PG05IMG.zip copy to sd card reboot do power volume restart it should do it itself don't shutdown until it is completley finished.

I did that but it won't downgrade. It says I have the newest version installed so it won't flash the "older .5" version. Any suggestions?

Make you rename it pull battery two button restart and it will load .5 I had no issues
Sent from my ADR6400L using Tapatalk

davwman said:
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Click to expand...
Click to collapse
Is that uninstall com.smithmicro.DM 1.0.0 ? Is this the right thing to uninstall for no OTA? Thanks
If so, I think I will uninstall this before I flash the new radio. What do ya think?

i don't see that file... on a side note, i updated the radio this morning and still no message to update so not sure if i'm in the clear or not

so what does com.smithmirco actually do? is it just an updater?

My phone seems to be stuck in the process. I can't locate a p50IMG on the SD card and before I can even open Titanium my phone starts to power down and tries to install the update, but fails. Any ideas?
---------- Post added at 01:51 AM ---------- Previous post was at 12:57 AM ----------
Finally think I figured it out for my situation. As soon as home screen loaded I opened up TasKiller, killed everything. Repeated that 4 times so that everything loading up with the phone was killed before it would reboot the phone. Went to app drawer and made a shortcut for Titanium right next to TasKiller. After this I went in and killed all apps again.
Now let's freeze some things via Titanium so it doesn't try to reboot to install an OTA. First I froze com.smithmicro, next I froze HTC DM. After these two I let the phone go while I messed around for a few minutes, after this I turned airplane back off. I checked TasKiller and noticed that an app MCC_OTA had opened, fearing this may be the cause I killed all apps again and went in to Titanium and froze this.
15 minutes later and I've had no issues with cell/data service. I can get into the market, update apps, receiving gmail/email, and Facebook working fine.

Pender1 said:
so what does com.smithmirco actually do? is it just an updater?
Click to expand...
Click to collapse
I am not trying to be an alarmist, but a description from Smithmicro's site sounds strangely similar to the description on the Carrier IQ site. I will let you be the judge.
"Device Management Suite™ (DM Suite) is a standards-based server solution for mobile device management, enabling mobile operators to remotely customize, provision, configure, and diagnose mobile device settings."
http://www.smithmicro.com/products/device-management-suite.aspx

Still running strong, no problems and no force OTA attempts.

Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
It got to the android man screen and got stuck there. Again pulled the battery and rebooted in to recover. Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Rooted running Team Gingerbreaton ROM. This is the second time in the last few months that the forced OTA has tried to run itself.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
Click to expand...
Click to collapse
Happened to me this morning too. Good thing the phone sits next to my bed (use it as an alarm) and woke me up since I would have oversleep without it. Of course, I lost two hours of sleep because of it since I couldn't get it working in my half-sleep state and just stayed up because I didn't want to be late to work.
I need a real alarm clock.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
.
Click to expand...
Click to collapse
Happened to me as well. Up at 4:30 roughly with nothing working. Cleared cache as suggested and phone is now powered up but no longer showing 3g or 4g, simply 1x so something is still wrong. Have to get ready for work at this point and will have to do some more digging.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery ... Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Click to expand...
Click to collapse
Thanks for that. I was losing my mind this morning. Woke up, grabbed phone, and it had the sad Android screen with the Exclamation triangle. Felt like Anakin at the end of Ep. III for a bit. Did a search for "Block update" and came to this thread. Now to flash a non-Verizon ROM so I don't have to go through that again.

Just got another OTA notification this morning, was able to delay it... WTF? I'm rooted running a custom ROM and it's still trying to push this updated.

Just an FYI, if you get the update. Revolutionary root no longer works.

I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??

zx12dak said:
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
Click to expand...
Click to collapse
I had the same issue -- I received the update even though I had not accepted or checked for it. Took my phone out of my bag at work and saw I was at the Android man and exclamation point screen.
I wiped cache and wiped Dalvik cache, and the update stopped. I did flash the new radios though for the .9 update and have been sitting fine on 4G for the last two hours.

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.