[Q] Problems after changing ROM - Droid 2 Global General

I installed Liberty 2.1.5. It wouldn't let me out of airplane mode. So, I reinstalled my initial ROM (I've done these steps several times. I know, I'm an idiot)
1. When booting, Liberty shows up but then I get the normal D2G Droid Eye. Obviously parts of Liberty are hanging around.
2. Now dialer won't stay open. It comes up and immediately closes. I can voice dial, but not finger dial.
Any ideas on what might have gone wrong and what I can do to fix it?

I did the same thing when I first got this phone. Liberty is made for the d2 not the d2g so it will cause those issues. The only way I was able to fix was flashing the sbf file and then clearing the cache partition. Starts you over from scratch but it worked.

Related

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

Reboot loop on ADP1.5H r3

My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.

FCs/soft reboot?

So so far, yesterday I've had the multi-touch keyboard force close maybe 4 times, the drag racing game 8, and a soft reboot. I have not rooted yet... holding off until there is more of a point. Anyone else having issues like this? I have 28 more days to do an exchange, I wanted to see if it's just my phone or not & either way I'll give it another week to see how it fares. Soft reboot occurred at maybe 40 hours or so of run time.
I use Go keyboard which has a far better layout and the swype ability as well, never had a fc. I dont play games. Have gotten a few fc's on various apps for unknown reasons, a few freezes in apps, but it happens so rarely that its not an issue. I did have to do a hard reset the day I got it though, but it was my fault.
sent from my Motorola Atrix 2 via Tapatalk
try doing a battery pull, not saying it would help but it definitely wouldnt hurt.
Fter rooting FC's also
After rooting (One-click method) and running Titanium Backup Pro to get a good backup of my phone. I now have a similar FC issue. Every time I try to open a contacts details, in the contacts app that starts, it will FC on me. The same thing happened to the phone app, works only if I dial a number from the keypad, click on a recent call in log, baam! FC I had to install GO Contacts/Dialer and they work fine. I tried to clear the cache/factory reset but the issue persists after I just loose all my info.....
Any way to Flash back to stock yet, think its a little to soon to root this racehorse....
I now have 3 apk's in TB that have a line through them. I cannot backup/restore/freeze the apps. Under the lined out app it says "No Backup yet"
com.motorola.blur.contacts.sync.yahoo
com.motorola.blur.provider.linkedin
com.occamy.andriod.motoxmayhem1lite
Anyone that can post these apk's so I could re-install/repair would help me greatly. I had this similar issue on my old cappy and replacing the app fixed it. I think when TB makes a backup and closes the app it some how actually deletes the app and/or corrupts it and then you have to replace it.
Rooting should no effect on the problems you are having. Did you freeze anything with TB, if so unfreeze everything, if not try unistalling it and see if the problems persist
If you are rooted, download ROM Manager and run fix permissions. That should help out with FC's.

[Q] Phone, contacts and messages keep closing

I have Galaxy S with Android 2.3.4 JVR and it works like a charm - with this one exception: sometimes (too often) phone, contacts and messages (sms) keep closing. This happens usually within a second or two after opening up them. There's no force close message, it just returns to the home screen without any warning. If I reopen it, it usually does the same a couple of times, but eventually I get it to open.
At first I thought this must be a memory issue. However, I have Autokiller installed (my phone is rooted) and I have usually >100M free memory. Then I thought it must be Autokiller killing the dialer, contacts or messages apps. BUT: this happened also before I had Autokiller installed, so it can't be that either. The strangest thing is that I tried installing GO SMS Pro and GO Contacts + Dialer, and even they do the same thing occasionally (close immediately after I open them), so it isn't a problem with apps either.
I am bedazzled here, could somebody please help me? This starts to get really annoying, since the dialer, contacts and messages are the feature you normally use most in your phone!
I have the exact same problem! Somebody, please help
the phone app and etc. seem to be corrupt or something
try reflashing.If you keep getting the problem then revert back to your previous rom =/
Is there any way to try to replace only the phone etc. apps without flashing the whole rom?
from my experience no but you can try replacing phone.apk sms.apk etc with the previous rom's apps
The funny thing is that I have a stock 2.3.4 JVR, so it should be stable.
Plus, did I mention that this happens only sometimes? Sometimes they work ok. But this happens often enough to be annoying. You know, when you would have to make a quick phone call you have to open the phone app like 3-4 times, only then you're able to make it. I wondered if the the problem could still be in the dialer, contacts and messaging apps even if the problem occurred only sometimes?
In addition, the calendar app has done this a couple of times. Could it be that there's a conflicting app that's causing this? If so, do you have any suggestion what it would be?
Autokiller made my phone do some really funny stuff. After installing it i was having random reboots and apps crashing so i uninstalled and problem solved. You said it was happening before you installed it though so im just guessing that you need to either wipe cache and dalvik then reboot or do a full wipe and reinstall of your rom. When you do the full wipe go into mounts and storage and wipe system too
Hi and thanks for your comment. What are the effects of wiping the cache and the dalvik cache? Do I lose important data? Or can I do it safely? Sorry, I'm a bit of a n00b with android. I suppose you wipe the cache in download mode, right?
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Whitest said:
I experience exactly the same issue as you-though I am on stock jvu.I come from 2.3.3, stock as well, using chainfire root both times.
Sometimes phone contacts and message s close immediately after opening them, often several times. and sometimes everythings fine
here you can find some information about dalvik and normal cache wipe..your data will be safe-only first boot will take longer.I will try wiping now, too-reporting back then.
Edit:
For now wiping seems to have worked well and fixed the problem here..I need some more testing though-will keep you up to date here
edit 2: damn! The issue's still there.anyone got more ideas?
G'day!
Click to expand...
Click to collapse
earthman5678 said:
I have the exact same problem with JVU and I had this problem with 2.3.3 but less frequent. I have no choice but to reboot the phone when it happen. I suspect it's caused by one of the widget (email and Go weather) that I put on the desktop. Going to remove the two widgets from desktop and see if it's help.
Click to expand...
Click to collapse
Okay, that sounds interesting - though I am not sure wheter a widget could cause this...
I am still running JVU but now with Galaxian Kernel instead of Chainfires root Kernel - flashed with SGS Kernel Flasher and still got root - and it runs very stable and fast 'till now. No more closing of phone, contacts and messages so far -.- since 2 days.
I'll tell you when it happens again, but so far it seemed to be a kernel issue for me...
I've been having the same issues with my Samsung SideKick 4G. messages would keep closing as I was typing them, I would lag and the key I pressed would "press again" like 15 more times, sometimes I just couldn't open a conversation, other times I couldnt answer phone calls cause the UI lagged.
That was all on stock firmware, and I got fed up with it so I tried to flash a custom ROM on it, and before I did that I had it OC'd to 1.2GHz which was actually pretty great. Needless to say, I screwed up on flashing the ROM and now I'm looking for firmware to odin back to stock. =\

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.

Categories

Resources