Database Develop

Installed Hero twice and having issues

I installed Hero the latest version and whenever I get the phone on it says "the process android.process.acore has stoped unexpectedly. Please try again" What do I do, I been without a working phone for almost 7 hours now

mikesx4911 said:
I installed Hero the latest version and whenever I get the phone on it says "the process android.process.acore has stoped unexpectedly. Please try again" What do I do, I been without a working phone for almost 7 hours now
Click to expand...
Click to collapse
Without making things too complicated, and to simply get you back up and running. just flash another ROM....
That way you will have your phone back in working order and you can do some more research regarding ROMs. Keep in mind that many of the Hero ROMs are still somewhat buggy but are coming along nicely. The good news is there are many Hero ROMs to choose from so picking another will likely fix your acore process force close.

im seriously ready to shoot this phone I wiped, cleared the ext 3 times and if i ever get to the OS cuz most of the time Im stuck at HTC and the little hero keep looping. I will wipe ext and alt wipe and try to load up a different rom

im seriously ready to shoot this phone I wiped, cleared the ext 3 times and if i ever get to the OS cuz most of the time Im stuck at HTC and the little hero keep looping. I will wipe ext and alt wipe and try to load up a different rom
Click to expand...
Click to collapse
Yeah..i think that would be a good idea. You can try cyanogen's rom. Probably the 3.9.10 version, which is a pretty fast and stable rom, and then just get Ted417's Hero theme(which I think is the best Hero theme out there) flashed on there to give you that Hero look minus the widgets of course, if that's the look you're going for.

eessel said:
Yeah..i think that would be a good idea. You can try cyanogen's rom. Probably the 3.9.10 version, which is a pretty fast and stable rom, and then just get Ted417's Hero theme(which I think is the best Hero theme out there) flashed on there to give you that Hero look minus the widgets of course, if that's the look you're going for.
Click to expand...
Click to collapse
that theme is garbage lol. It wont even install, I tried like 4 times. WTF!!!!

Are you using ext4?

i got it working lol

mikesx4911 said:
i got it working lol
Click to expand...
Click to collapse
Mind telling us what you did to fix it so others may know if they have the same problem?

Hi there, I'm having the same problem.
Hero was fine until I did a factory reset (I'd cleverly managed to lock myself out of it via the security swipe).
Anyway, did the factory reset and now I get the android.process.acore has stopped unexpectedly problem.
I'm not that keen on installing other ROMs at this point, just hoping you can share your solution.
I'm guessing but it seems to be connected to my contact card within contacts. (If i wipe the info in that and log out of facebook the issue stops).

trstn said:
Hi there, I'm having the same problem.
Hero was fine until I did a factory reset (I'd cleverly managed to lock myself out of it via the security swipe).
Anyway, did the factory reset and now I get the android.process.acore has stopped unexpectedly problem.
I'm not that keen on installing other ROMs at this point, just hoping you can share your solution.
I'm guessing but it seems to be connected to my contact card within contacts. (If i wipe the info in that and log out of facebook the issue stops).
Click to expand...
Click to collapse
What I did was load a different rom non hero first, than updated to a hero rom and it worked. Because I couldn't figure out how to get rid of it lol. But personally I stopped using the hero rom, there to slow, and missing to much stuff such as bluetooth and etc.

mikesx4911 said:
What I did was load a different rom non hero first, than updated to a hero rom and it worked. Because I couldn't figure out how to get rid of it lol. But personally I stopped using the hero rom, there to slow, and missing to much stuff such as bluetooth and etc.
Click to expand...
Click to collapse
for what its worth. hero itself is not a theme. and neither is cyanogens roms. when you said that "this theme is garbage" you may have been talking about the wrong item.
also to get rid of a rom, just wipe, plain and simple.

Camera and camcorder force close after upgrading to Cyanogen 4.2.12.2

Just today I upgraded to the latest Cyanogen release (4.2.12.2) on my G1 from pre-4.1.99, and any time I attempt to open either the Camera or Camcorder, it Force Closes, and returns me to the home screen.
I've tried cleaing the cache/data for both the Camera and Camcorder, but that didn't appear to fix the issue. I've also run the fix_permissions command as well, which didn't help either.
Any ideas on what might help fix this problem?

run fix_permissions from console... and post in correct section next time

I apologize for having posted this in the wrong section - where does it belong?
Also, I stated in my OP that I ran the fix_permissions command; from the console was implied.

In the 4.2.12.2 thread.

Thread Moved to Q&A.

I just tried two things: first just wiping and flashing the Cyan Rom again, and that didn't fix it.
Then, I wiped, installed the 1.6 base rom, and then Cyan Rom on top of that, and I still get Force Closes for both the camera and camcorder.
So, I'm still stuck. Any more ideas?

Do you have any apps that use camera (Google Goggles, Barcode Scanner, etc)? You may have to wipe data from those as well.
Also, do you have apps2sd? If so, wiping is not as effective as it is without it. If you do apps2sd then you need to run this from terminal
Code:
su
rm -r system/sd/dalvik-cache/*
reboot
Good luck.

borodin1 said:
Do you have any apps that use camera (Google Goggles, Barcode Scanner, etc)? You may have to wipe data from those as well.
Also, do you have apps2sd? If so, wiping is not as effective as it is without it. If you do apps2sd then you need to run this from terminal
Code:
su
rm -r system/sd/dalvik-cache/*
reboot
Good luck.
Click to expand...
Click to collapse
I tried running these commands in the Terminal Emulator, and after the reboot, I still get FCs when trying to open the Camcorder and Camera.
I collected the log, and have attached what I believe to be the relevant portion of it to this message.
Any more ideas?

same here!!!
I am having the exact same issue as you show in the log file
have had some success in reflashing base rom but it only works for a day or so (or hours in some cases)
believe it to be an issue with the drivers but something is killing the camera every time
have removed all apps and reflashed but now it just keeps fc
if any of the devs working on camera issues could have a look please help
cheers
j.

Same thing here.

Same problem here, sucks.

Same HEre 2 =[

Androiid=D said:
Same HEre 2 =[
Click to expand...
Click to collapse
same here, and I tried:
going back to 4.2.8 (where camera last worked for me, before going straight to 4.2.13),
I tried wiping,
I tried removing and and re-making the ext3 partition
I tried reflashing the radio (2.22.19.26I from http://code.google.com/p/sapphire-port-dream/)
My camera is still dead (force closes)

If you have the same issue (camera force closing, flashing older OS not fixing the issue), PLEASE go to Cyanogenmod project Google Code website and click the star next to "Vote for this issue and get email change notifications" on the bottom of the page. You have to be signed into your Google account.
Voting for this issue will raise it's priority (crucial, as it seems to affect a small number of units so far, but it's a show stopper).
Cyanogenmod project Google Code website:
http://code.google.com/p/cyanogenmod/issues/detail?id=1037
Thanks!
Blaz

Much respect for Cyanogen and all he does for further the HTC Dream: G1 community.
However, if you are having so many issues maybe its time to change to
another Rom altogether. Just my 2 cents..

legend221 said:
Much respect for Cyanogen and all he does for further the HTC Dream: G1 community.
However, if you are having so many issues maybe its time to change to
another Rom altogether. Just my 2 cents..
Click to expand...
Click to collapse
Ummm, I've only one issue: camera not working. Thanks for the pennies tho

blazzr said:
Ummm, I've only one issue: camera not working. Thanks for the pennies tho
Click to expand...
Click to collapse
Here's a few more pennies my good man, if the camera is a deal breaker then consider my above comment and change Rom.
Your choice, that's why this community should never go away.
Freedom to customize as you see necessary and fit is the ultimate reward.

legend221 said:
Here's a few more pennies my good man, if the camera is a deal breaker then consider my above comment and change Rom.
Your choice, that's why this community should never go away.
Freedom to customize as you see necessary and fit is the ultimate reward.
Click to expand...
Click to collapse
have tried other roms but i still get the force close so not really a cyan problem methinks

cqms13 said:
have tried other roms but i still get the force close so not really a cyan problem methinks
Click to expand...
Click to collapse
I too a while back had problems installing roms and constantly seeing FCs on my phone. .
The way I fixed that problem was using a bigger/better/faster microSD card I already had.
( @Cqms: I see you already have a newer microSD however, perhaps formatting it after backing up your contents first suits you and then copying everything back once finished. Finally wipe completely/flash Rom and you're set).
Formatted it fat32, since I copied my data on the pc first I copied what I had to the new one.
And finally installed what in my opinion to be one of the best Roms (see my signature) through the wipe/flash procedure and have been extremely happy since.

Camera is back (sort of!!)
Ok as suggested by Legend in above post - wiped formatted etc and flashed super D ROM
Camera comes back but has some kinda solarisation effect which I cant seem to get rid off.
Added to this is my contacts and dialer keep fC ing on me so this ROM is a non runner for me even with a semi working camera
getting closer to the fix though
maybe ima try reflashing cyanogens latest again and see if i can sort the weird effect on the camera
heres hoping
j.

After booting aospCMod 2.3.2

So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.

Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App

okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.

i tried also and still no luck .. i hate this

to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.

So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.

I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.

i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!

sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass

il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™

Yeah I'm using clockwork 2.5.0.1.

sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.

So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App

sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH

Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).

got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?

sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!

There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.

mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.

touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help

[Q] CM 7.1 with all the goodies

I'm having a problem installing CM 7.1 and all the speed/memory tweaks. Ive used MANY different roms with alot of tweaks but this one i driving me crazy. Im trying to install CM 7.1 in CWR 2.5.0.7 with the following tweaks...Firerats 1.5.9 auto patcher and KERN 2.6.35.14-10sept-v1 .....the problem is that i can not get it to boot!!!! if i dont install firerats the rom doesnt boot and goes back to CWR...if i do install firerats the screen just hangs on the htc logo...but without the tweaks CM7.1 boots fine
Please help!!

I did the following with success (this is from memory, hopefully I don't miss anything), I'm using firerats 1.5.8. I did not use a single fr patcher.
First, I flashed the firerats REMOVE zip, just to make sure I was really starting over. then flashed the latest CWM unofficial recovery...5.0.2.6.
rebooted to recovery after each step above though, and repeated wipe data/factory reset, wipe cache.
for firerats, had the mdpartmap settings at 125, 20 (just being extra cautious there, I'm seeing some lower numbers bandied about).
Anyway, from the pretty blue recovery screen, I then flashed fr-recovery, (I think it tells you to reboot to recovery again when done, possibly wiping again, anyway, it tells you) then flashed cm 7.1, gapps, kernal, and finally, fr-boot.
Seems I've heard of folks having some difficulty if they don't use a newer recovery, perhaps others can chime in on this.
After some initial settling in and reboots (it was a little hot at first, a few things were a little flakey), everything seems to be running great. I've only had it on here a few days, and I have not tweaked any performance settings, but so far, gps has been rock solid (isn't this ALWAYS a sticky point for some?) and runkeeper has stopped being so crash happy. Need to see how these things behave with age. A clean installation fixes a lot of things for awhile.

Okay, fired up gps status app, and boom, reboot. But like I said, haven't tweaked any performance settings, left everything at defaults. Will tinker eventually.

wow!!! thank you so much for the very fast reply. I am at work at the minute but i am going to try this ASAP!! Thanks again.
I will keep you informed as to how this worked out. Looks like it should work though

Ok thats awesome!! i got it all to work but i can not get android market to work. I just get FC everytime.
Is there a fix for this?

verybigleen said:
Ok thats awesome!! i got it all to work but i can not get android market to work. I just get FC everytime.
Is there a fix for this?
Click to expand...
Click to collapse
Hmm, not sure, did you use the gapps from the OP for CM7.1? Could try redownloading that and flashing it again.
also, what were your firerat settings in the partmap file? Just checking, in case you didn't use mine, which were generous, as I said.
That rather larger second number in the partmap file resolves a lot of market issues, I never have to apply any "market fixes"

My fault. I used 125 2 in the mtd instead of 125 20....worked great!!! now i can use the market...thank you so much!!! just have ooooooonnnneeeeee other small problem.
Now by busybox wont work. Keep saying no root access when obviously i do...and also i can not fix permissions in rom manager..theres always a problem eh.
Hope you can help...you've been great so far!!! got loads more internal space now

Hrm...I have to admit to never using busybox, at least not directly, I usually just install it if asked when I install/update Titanium Backup (after checking the allow unknown sources in applications settings). Are you trying to execute busybox from terminal or something? Apologies if you tried this but if you have Titanium (you should if you don't), then do this:
Go to titanium backup, go to problems then it will install busybox
I just cut and pasted that from ... somewhere.
verybigleen said:
My fault. I used 125 2 in the mtd instead of 125 20....worked great!!! now i can use the market...thank you so much!!! just have ooooooonnnneeeeee other small problem.
Now by busybox wont work. Keep saying no root access when obviously i do...and also i can not fix permissions in rom manager..theres always a problem eh.
Hope you can help...you've been great so far!!! got loads more internal space now
Click to expand...
Click to collapse

So I finally figured it out. I downloaded the cm nightly instead of stable and everything worked great.
Thank you so much for your help!!!
Sent from my HERO200 using XDA App

Just wanted to say. Just installed the new cm nightly and the new jaybobs kernal ....amazing...the new kernal is super fast and every body should use it! Its the Oct 22 build..I'm flying now
Sent from my HERO200 using XDA App

[Q] X8 reboots by itself

Hi all,
this is my first post so first of all I want to say how amazing this community is !!
I've installed gingerDX v018 just following the xda instructions and all has gone smoothly.
Anyways, I'm posting 'cause sometimes my x8 reboots by itself, usually during the night (each time I heard the logo animation alert ). I guess the timing is not significant, but it happens quite every night.
Do you have any idea of what could it be?
There is some x8 log I could read from or may I use the terminal emulator app?
P.s. I didn't flash the kernel, so I'm still using the stock K. No overclocking apps (not yet).

Do a full wipe. The GingerDX thread says there's no need to do a full wipe after update, that must have confused you.

if what Chris95X8 said dosnt work then your stuck for a while until someone makes a -all-in-one sorta fix. i used to have this problem and after a while it rebooted itself and it got stuck in a bootloop so do the full wipe as soon as posible imo.
i did a full wipe and now its back to normal. no more auto reboots either now.
if that dosnt work then reinstall the rom.

I thought I did. I mean, after the installation I did a full wipe to avoid reboot looping I experienced during my first time installation.
My installation steps actions:
- installed v018 zip
- installed extra zip
- ran Factory Reset (full wipe) option
- ran Wipe cache partitionoption
- reboot phone
Did I miss any steps?

wilbso said:
if what Chris95X8 said dosnt work then your stuck for a while until someone makes a -all-in-one sorta fix. i used to have this problem and after a while it rebooted itself and it got stuck in a bootloop so do the full wipe as soon as posible imo.
i did a full wipe and now its back to normal. no more auto reboots either now.
if that dosnt work then reinstall the rom.
Click to expand...
Click to collapse
If I run out of options I'll try to install the v019

Anªk|n said:
I thought I did. I mean, after the installation I did a full wipe to avoid reboot looping I experienced during my first time installation.
My installation steps actions:
- installed v018 zip
- installed extra zip
- ran Factory Reset (full wipe) option
- ran Wipe cache partitionoption
- reboot phone
Did I miss any steps?
Click to expand...
Click to collapse
hmmm you didnt miss anything...i will search around for an answer for you...if there is one...

wilbso said:
hmmm you didnt miss anything...i will search around for an answer for you...if there is one...
Click to expand...
Click to collapse
Thank you.
In the meanwhile this w/e I'll try to disinstall one app at a time, to see if there are some conflict. It has rebooted just 5 minute ago.

i read that u can try to use another memory card for awhile to check if the problem still happening.
i got the same problem too, and i tried using another memory card but it still happens. lastly, i sent it to the shop and the shop send it to the factory and it gonna take 3 weeks until i got my phone back..

maliceomalice said:
i read that u can try to use another memory card for awhile to check if the problem still happening.
i got the same problem too, and i tried using another memory card but it still happens. lastly, i sent it to the shop and the shop send it to the factory and it gonna take 3 weeks until i got my phone back..
Click to expand...
Click to collapse
oh man, thats a bummer... heres some smileys to cheer you up
there you go.
---------- Post added at 08:00 PM ---------- Previous post was at 07:54 PM ----------
Anªk|n said:
Thank you.
In the meanwhile this w/e I'll try to disinstall one app at a time, to see if there are some conflict. It has rebooted just 5 minute ago.
Click to expand...
Click to collapse
ok, some answers show that it is either the rom or battery, they also suggest to have it sent off to have it looked at, see if anything is mucked up or something. sorry if it isnt much but its all i could find so far

maliceomalice said:
i read that u can try to use another memory card for awhile to check if the problem still happening.
i got the same problem too, and i tried using another memory card but it still happens. lastly, i sent it to the shop and the shop send it to the factory and it gonna take 3 weeks until i got my phone back..
Click to expand...
Click to collapse
Hope they will solve the issue. let us know if they will
wilbso said:
ok, some answers show that it is either the rom or battery, they also suggest to have it sent off to have it looked at, see if anything is mucked up or something. sorry if it isnt much but its all i could find so far
Click to expand...
Click to collapse
Thank you wilbso, sending it off will be my very last resource. Anyway for now I've removed weather widget from the lockscreen and Homescreen, just to exclude any (?) refreshing data problems. Next step will be to install some task killer and so on.
I'll write if anything work it out!

Coverage
How's coverage in your area?
I had frequent reboots on low signal areas (very bad) and the phone tried to connect 3G to check e-mail. Anyway, after each reboot, I cleaned dalvik and cache, and then eventually it went away after moving from CM7 to GingerDX.

I think another possible problem is the ram cuz you said that you dont use task killers so the problem may be the low ram(every gb problem)if you confirm that this is the problem i sugest you should use advanced task killer form market

I don't think it's a ram problem, I suggest a full wipe an pay attention when you restore, do not restore system app or app data, the problem could be there...

crazy x8. Full wipe is the solution for prob in almost cases in x8 using custom roms. Wierd

@Chris_Castro:
2g signal looks stable, 3g poor, but at home I'm using wi-fi. But just to be sure I'll check the force 2G signal option, so we will see.
@X8invisible13:
I had the same idea yesterday, so I've installed Memory Booster - RAM Optimizer, here my ram data:
total memory: ~ 175MB
memory avaiable: ~26MB
and reading here and there they look to be average values. But one of the next tests will be to install the latest gingerDX rom, or some other cool roms and test each app at a time.
@evil_chris:
mmm, I'm quite the noob here, so I don't have any backup data or backup apps. I was playing around with HS/LS, sliders, icons when I experienced first problems, so had no time to deepen backup systems.
But I got what do you mean, so as I said, the next installation will be a naked one.
Last episode happened yesterday morning, I checked the locked screen, w/o unlocking it, and after 20 sec it rebooted. Just after I logged in it rebooted again
Anyways Thanks guys

I Cleaned Dalvik and cache, and removed the overclock and now looks good