I have a brand new HTC Wildfire bought just a few days ago in India,While using the phone I frequently get a dialog telling me that "android.process.acore" has stopped unexpectedly and needs to be closed. I acknowledge the dialog by clicking "Force close". This seems to happen regularly, every 10 or 20 minutes or so during use.
If any one has proper fix please do respond.
I had this once after flashing Wildpuzzle, i just restarted the phone and everything was fine.
whts wild puzzle, I have done hard reset still the exist.
I have this Problem too.
"android.process.acore" FC me all 5 sec.
I turn off all Auto Sync Options (I read this was a major problem in the past), but it still doesn't work.
May you can help me?
I use CM 6.1 signed.
I'll need a solution, because that's very annoying.
Thank you in advance.
Sorry to revive an old thread but i flashed a new Rom last night and after rebooting i now have this message appear after every action I make on the phone. I have tried flashing several Roms but all seem to have the same problem. Below is as much infomation i can get from the phone. Hopefully someone with great wisdom will be able to help me,
Kernel Version
2.6.35.14-Sympfinity+
[email protected] #13
Tue Apr 17 16:52:19 CEST 2012
Mod Version
Miui Buzz Beta 4
Build Number
MIUI-eng.rmcc.20120314.155025
ClockworkMod Recovery
5.0.2.0
HBOOT
6.01.1002
Radio
3.35.20.10
if you need more information please mention
I have tried Fixing permissions in Rom Manager also.
Please If you can Help.
Did you wipe all partitions before flashing??
Sent from my HTC Wildfire using XDA
I found that you have to delete data from Contacts Storage. It seems to have fixed it!
Related
Hey Frnds, Sorry if this was asked before but, i am so confused after reading so many problems and solutions too on here as well as on net....
I need a little help from you on my Desire Bootloop problem...
i have the problem since a few days.
first time i notice it,was when the desire was charghing and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with Mpas, wifi etc the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
i wanna commit that i have unbranded (Purchased from Indian grey market b4 official launch of desire in INDIA) phone and i am unable to send it to HTC repair center.
i tried different ROM's available here on XDA but, same problem with all.....Is there any way to unroot the phone (may solve my problem)
Below are the details of my desire
Bravo PVTI SHIP S - ON
HBOOT - 0.08.0000
MICRO - 03id
TOUCH PANEL - SYNW0101
RADIO - 5.09.05.30_2
MAR 29 2010, 21:34:33
I am using CM7 now.
i also would like to add few observations of past 2 days...Might help you to find right way....
After reading so many threads on reboot issues of Froyo....i shut off my Mobile Internet (2G - Vodafone).Phone had never restarted (Once only in 2 days after a long phone call i.e. 20 Mins+)
i tried to on 2G 4-5 times to get my mails...All time immediately restarted...
so, my conclusion is because 2G net connection....
Please try to help me ..... Thanks Again
Someone please atleast try to give me some directions.....
Sadly bootloops are a part of all gingerbread roms at the moment, it's a fault in the code from Google.
The latest 2.3.3 builds are supposed to resolve this, though I don't know how long before CM will have this integrated.
The only things I can suggest -
a) reboot manually every day or two - chances of bootloop are worse the longer it runs
b) if you get a bootloop, hold power + vol down + trackpad and it will break the loop without having to pull out your battery.
M.
mattman83 said:
Sadly bootloops are a part of all gingerbread roms at the moment, it's a fault in the code from Google.
The latest 2.3.3 builds are supposed to resolve this, though I don't know how long before CM will have this integrated.
The only things I can suggest -
a) reboot manually every day or two - chances of bootloop are worse the longer it runs
b) if you get a bootloop, hold power + vol down + trackpad and it will break the loop without having to pull out your battery.
M.
Click to expand...
Click to collapse
That isn't necessarily true. I've no 1 bootloop and I have flash Gingerbread roms dozens of times. I find if you reflash the rom it usually boots up fine.
I haven't had bootloops either (using Redux), but in the ROM's thread, everybody who does solves the problem by flashing a new kernel (usually Coutts). I've never used CM, so I'm not really sure if it helps, but you could give it a try Btw, please be careful if the kernel you're applying does undervolting or overclocking, and make sure you're not flashing a FroYo kernel while using a Gingerbread system or vice-versa
Hey guys,
the strangest thing since i'm using android happened to me right now.
I realized that my DHD starts to lag after 2-3 days, a reboot fixes it, (USB debugging always enabled) but that's not the problem :=)
so i wanted to restart!
all apps stopped working unexpectedly....
really everything, launcher, there are masses of popups coming up, no idea what really happened.
the only thing i know, htc sense seemed to work (i was so intelligent to try to start launcherpro, which created a default shortcut, so then everything including launcher pro stopped working, no chance to to anything (usb connection not detected... nothing)
popups just reoccur directly after clicking them away. no idea at all.
i found this:same problem on another phone @xda
but there hasn't been a solution too.
so i just wanted to tell anyone out there experiencing the same with a dhd.
u're not alone.
i'm reflashing. (another rom, it was revolution hd 3, but i think its not rom related - but i have to mention, the stock rom - used for 2 months before- never had anything similar - rev. hd was just in use for a few weeks now (1 or 2).
howdi
cV
update:
guys this really suckz, i dont know whats different with my DHD and the combination of revolution HD rom, but this is the second time this happened!
the first time, i realized (not as written above) i was using rev. HD 2.1
now it was on 3.0
i know, there's a 3.1 out there, but i really dont want to test it.. something's really strange here? (same error happened another time :===/)
I suggest you to reset your Desire HD
thanks,
hennailiao said:
I suggest you to reset your Desire HD
Click to expand...
Click to collapse
... directly flashed a new rom (there was no other possibility)
thanks for the response, i hoped that somebody can exchange some experience with this problem to prevent it in the future
greets,
Problem solved on my HTC HD2
Just solve the problem on my HTC HD2 applications force to stop error, no need to soft of hard reset required no need to update or re-install ROM, Go to Manu >Rome Manager ( My version is v4.8.1.3 > Utilities > TAP ON Fix permissions ( Fix file system permissions, this often fixes force close problems) after waiting few minutes reboot and enjoy ...............
Hi guys:
I am really desperate now... my phone only seems to work with the official ROM, everytime I rooted, and installaed a Cooked ROM (GB ROM) very soon (in a minutes of using it) it will hang or freeze or reboot.
I explain all backround:
1. firstable I have my desire working for awhile with many cooked ROM (Froyo), after months,the phone started to reboot everytime, so I have sent it to the SAT, and they changed the motherboard. and give it back to me.
- The new motherboard is
PVT4
HBOOT 0.93
MicroO 0,51d
2. I rooted it OK (using unrevoke methos)
3. Flashed a cooked ROM => then is when the problem starts, everything after falshing is OK, but after a few time of usage with the cooked ROM, then the phones starts to freezes randomly.
some further info:
- tried with Neophyte ROMs Reflez 2.0.9,2.1.0...2.1.6 => same issue
- tried with LeeDrOiD V2.5.0 FINAL | 28th May l Official => same issue
- tried with LeeDrOiD GB 3.0.6 => same issue
if I go back into the offical ROM (by unrroting method) using the "RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed" => Issue is NOT reproduced!
- In all cases, I did try to keep ONLY apps coming from the flasehd ROMs, to make sure any app is causing the issue.
- I have tried using another miniSDcard (8GB class 4) => same issue!
Is it anything wrong with the new motherboard?
Is there anyway to check logs or trace why is freezing?
Any clue?
Thanks for your advise!
best
SCesarin
(please don't advise me to keep using the official bored ROM)
No body give me a clue or help on this?
Please
Sent from my HTC Desire using XDA App
I have the same problem. I have noticed that most times my desire freezes when I download something over mobile network. So maybe the problem is in A2SD? I'm going to try with Cool Kingdom Rom, because I already have EXT4 Partition.
Deivino said:
I have the same problem. I have noticed that most times my desire freezes when I download something over mobile network. So maybe the problem is in A2SD? I'm going to try with Cool Kingdom Rom, because I already have EXT4 Partition.
Click to expand...
Click to collapse
Thanks a lot Deivino for your comments.
Please keep me posted about what happens with your "Cool K. ROM"
hope your issue is gone then.
Mine still present, I can use ONLY the official ROM.
SC
So I had no luck with Cool Rom. It still freezes, but much less now. Also these freezes are very random now, mostly when screen is off. I haven't flashed jet the newest radio and ril, but I don't think it would fix it either. I was thinking about unrooting, but when I did, I got less than 30% battery error with full battery. So I have no idea how to fix it or what is even causing this freezing.
Hi Deivino
Since I've unsuccesfully tried with many cooked ROMs, finally I have decided to take the phone to SAT, which fortunately still on guarantiee.
Let's see what do they find...
good luck with your phone,
best
I managed to unroot my desire and now running official android 2.2 what htc provides and the problem still occurs for me. I don't see no other way but to send it to warranty.
Hi Deivino
I did the same, actually many things unsuccesfully as you see in my first post.
Finally, I sent it to warranty, and they gave me back already a new device!
Now, it works OK.
So, unfortunately, the issue was not fixed at all, either I don't know what caused the issue.
regards
SCésar
Try cyanogenmod.. it's THE singlemost stable ROM you can install on your phone. Never fails.
I agree.. never had an issue with CyanogenMod ROMs
Sent from my CM7.1 Desire using XDA App
Hi Guys,
thanks, finally I sent my desire to SAT, and they gave me back a complete new one!
So, with the old one I did all in my hands unsuccesfully as I explained in my first post, so I didn't try CyanogenMod ROMs therefore I will never know if it would works!
Anyway, thanks a lot guy for all your suggestions.
best
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
tonan791 said:
Hi XDA people,
This is my first post in XDA and its a problem i am facing. Whenever i switch to GSM/WCDMA Mode and start using the 3G internet, the phone restarts with 5 - 7 vibrating alerts. I did searched this forum before posting and got similar posting for HTC Buzz
BIG ISSUE: 3G problem..!!
http://forum.xda-developers.com/showthread.php?t=1823816
Went through that and found out that by updating the radio this problem can be fixed, so went ahead to find the udpated radio and hboot and updated them using RUU, got a tutorial for the same in XDA forums
So updated Radio from 7.53.39.03M to 7.54.39.28M
Hboot : 1.08.0000
But the problem is still there, as soon as i switch it to 3G mode, i can see the H symol comes up for the GPRS and the network changes to R (Roaming- no clues why this happens but i am fine with this as long it works.) and within minutes it restarts making 5-7 vibrating alerts before rebooting.
can someone help me with this, is there a way to fix this for HTC Wildfire S (Marvel)
Kernel : [email protected] #2
Android version : 2.3.5
Htc Sense : 2.1
Software Number : HenseMod 7
Click to expand...
Click to collapse
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
quack75 said:
it happened to me, the only solution I found was flash the backup of my original Rom Sense PREROOT, turn on 3G and check that it worked.
Then without turning off the 3G flash another rom clean (a bit like the problem of the gps).
is a bit long but I was going crazy, my Willy sometimes restarted.
it may be useful with my HTC Buzz it worked ... but you're rooted?
Click to expand...
Click to collapse
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
tonan791 said:
Yes i am rooted, also i dont have any stock backup
I read in the forums that in HTC buzz if you update to an older radio then wipe cache then update to a higher radio version it fixes it, but i need to find out if that would work for MARVEL, and what would be versions that i should switch to.
thanks for the help
Click to expand...
Click to collapse
tonan791 said:
Hi Eventcom, i went through the forum and found that you too had this same problem of bootloop after switching to 3g. I see that you have Buzz, just wanted to know will this simiar fix (update older radio, wipe cache, update to newer radio) can be applied on HTC wildfire Marvel as well.
I have posted my question after a lot of search, got similar threads for BUZZ but none for MARVEL, can you please help.
http://forum.xda-developers.com/showthread.php?p=31998311
Click to expand...
Click to collapse
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
I found this tread
http://forum.xda-developers.com/showthread.php?t=1485345
if you do not solve in any other way you could give it a try
I do not know the Marvel, but the Buzz htc are not all the same, the same solution to different results :silly:
eventcom said:
Well, I don't know anything about the Marvel. Both phones are quite different besides their names and enclosure.
Anyway I don't think that your phones radio will be touched when flashing a ROM or restoring a nandroid backup or that you could wipe, clear or format your radio partition - so in theory it could work with the Marvel, too.
A short explanation about the whole thing: The Buzz has well known issues with the radio (no GPS or BT, WiFi probs) - even directly after rooting and flashing the first custom ROM. There's also a chance that something might go wrong or get messed up when flashing different ROMs, installing tweaks etc. and the problem is that the radio resides on a separate partition which can't be wiped or formatted. All this sounds pretty logical to me but I'm not a developer so I might be totally wrong
The solution seems to be to flash a different radio (older/newer doesn't matter) to "overwrite" the current one - and sometimes reflash the current ROM again.
The problem I had has been hard to spot and even harder to solve. Luckily I found out that switching on 3G initiated the reboots (after quite a while and by accident, really). I made a lot of tests and could put it down to that (WiFi, 2G had no probs - phone rebooted only when switching to 3G or switching on data when 3G has been activated/chosen).
Furthermore I found the "solution" by accident, too: I reflashed the current radio without any success. Then I also tried an older radio - no success. So, as a final attempt, I started to download a RUU to reset the phone to factory condition.
The download server has been awful slow - it took ages to download the file - so I (almost randomly) decided to flash the previous radio again.
I couldn't believe it: that did the trick. (Luckily) I rebooted again, switched on data and 3G and noticed that the phone didn't reboot anymore.
So if you're able to flash a different radio - just give it a try. For the Buzz you need to be S-OFF to flash a radio - no idea about your phones.
I'd be glad if that would work for the Marvel, too :fingers-crossed:
Click to expand...
Click to collapse
Thankyou Eventcom, i will try the method, i am searcing for the Radio to downgrade and upgrade too, i did find a link here in xda will search for that again and see if that resolves my problem, thankyou for the details, appreiciate it
Hi.
Long time reader, first time poster. Or a "noob"
I have flashed the release of Evervolvs excellent P1 JB a few days ago. Everything worked fine up until today when the OS froze. I rebooted and it froze again. I rebooted and now I do not have any data connectivity. I have the H but the bars are constantly grey instead of blue as per usual.
When I installed it I made a back-up. I have flashed that and the problem still occurs.
I have done a full wipe and reflashed and still the same problem.
Could the radio firmware have become corrupt?
I have to confess I am not experienced in flashing a new radio and I am somewhat apprehensive of doing it.
I have rooted, S-Off and have a 1GB EXT4 partition.
Any help would be greatly appreciated.
HTC Desire - Was Orange branded but unlocked.
UK Giffgaff Network.
Jelly Bean: Evervolv Turba 3.1.0p1
Baseband Version : 32.56.00.32U_5.17.05.23
Revolutionary CWM v4.0.1.4
Bravo PT4 Ship S-Off
HBOOT-6.93.1002
Microp - 051d
Radio - 5.17.05.23
Dude...what do you expect? It's a pre-alpha.
You just flash a radio from recovery. Not such a big deal.
Also, last time I checked there was a dedicated q&a thread for that. Did we really need another praise here?
Sent from my HTC Desire using Tapatalk 2
@ Lars: I know what you mean. It is a nice mod but nog really trustworthy for everyday use. Losing the connection and fc, sometimes takingout the battery and reboot is the only solution.
Sent from my HTC Desire using xda app-developers app
It happens, however I've never had any major issues with P1 so far. It's pre-alpha, but I believe fully suitable for a daily use. You can always reflash it or do a factory reset if you bump into any problems. I would have expected people to be prepared for occasinal problems while using custom ROMs If reflashing and wiping everything didn't help, I would try a different ROM. If that does not help, you are probably experiencing HW problems.
Thanks for all the replies.
It turns out it was a network failure, but it all coincided with my phone rebooting
Before I look a total chump, I would like to add that I was using Evervolvs ICS and lost data connectivity after long periods of inactivity ie overnight. I had to turn data connectivity on and off to get it to connect. I thought this problem was one and the same with JB. So there was logic to my madness.
I have narrowed the rebooting issue to the Facebook widget, so I have removed it and all is stable :highfive:
Would anybody recommend flashing a more up to date radio or should I stick with "If it is not broke, dont fix it" mantra? Which I am inclined to do.
Thanks again for the replies.
Lars