After updating to JF 1.43, I keep getting this error when I try to make a phone call. I can actually make a call, meaning the radio is working, its just after dialing I get this error but the call goes on, but the black screen that displays the contact picture and number isn't there, its just the homepage with the green icon in the notification bar. How can I fix this? I have attempted this update 4 times now.
Solemn Wishing, are you still getting that message?
I have the same problem, and as of now, my phone is unusable.
I reported it here:
http://code.google.com/p/android/issues/detail?id=1864
My comment is #6
edit: I think I found the answer to what causes that bug! See my comment #7 at the above link.
A wipe solved this problem for me.
Yeah, the wipe will reset you back to the default of select automatically, but if you do it yourself, you don't have to wipe!
It's a weird bug, because it only seems to happen when you are locked onto one network, and restart your phone in an area where that network isn't available.
If you are driving around and don't turn your phone off, you won't notice the problem.
edit: sorry posted in wrong thread
edit: sorry posted in wrong thread
Related
So I flashed my phone to the HyperDragon III ROM a few months ago. Everything works smoothly and I had no problems at all. Only small issue was the keyboard lag and that issue was addressed in a separate post.
After using the Keyboard Lag fix, my phone does not fully load. I get to the splash screen and everything and then the Start Bar loads as well as the bottom Calender and Contacts menu. The screen will display my background and it will say "Tap Here to launch TouchFlo". I tap there and nothing happens.
I've been patient and I let it sit there and nothing happens. I can get to my text messages but it runs unusually sluggish and will display an overview of all messages but when I try to open a specific message, it freezes up.
This is actually the second time this has happened. The first time I removed the Keyboard Lag CAB but the issue continued. I left the phone alone and reset it a few times and miraculously it started working fine.
I have since removed the Keyboard Lag CAB completely yet it has still happened. Anybody else have the same problem or have a solution? Any help would be great.
Never flashed HDIII rom's so I have no idea why you are having that problem. Have you already post this issue on the rom's threat?
not-available said:
Never flashed HDIII rom's so I have no idea why you are having that problem. Have you already post this issue on the rom's threat?
Click to expand...
Click to collapse
Not on the HDIII thread. I did originally post my problem on the Keyboard Lag thread. 10 minutes after posting the first time my phone went back to normal so I went back and edited the post.
So try it on the HDIII threat. That's the best where you can get help related with that rom.
Also, maybe some other user had already that problem and have some solution or is waiting for some. Ah, before post the question, that some time to read the full threat... your answer can be already there.
Thanks. I just figured I would post. I've been reading the thread for a while now. Its over 900 pages so I thought I would ask first
You can also try to do a search on that threat http://forum.xda-developers.com/showthread.php?p=3102963&nojs=1#goto_threadsearch
Happy New Year
So my phone just started working again. After about an hour or so of resetting and stuff it displayed Lauching TouchFlo and its normal again. I'm just afraid to ever turn it off again.
did anyone solve this problem?! cause mine just randomly stopped launching touchlo and I dont know how to get out of it?!
Closing thread
Please post issues with HyperDragon rom in the HyperDragon thread, instead of opening new ones.
Peace,
Joshua
Edit: error message says android.process.acore
Don't really quite know what it is, but that's what I get
Not quite sure as to the rarity of this problem. But it has happened about 3 times already. Sometimes while on the phone, I get the error message and askes if I want to force close it. No matter which option I choose, my phone will go back to my sim lock screen as if it's booting up. Matter of fact, it is booting up.
Just wanted to know if this is isolated or if anyone else got this. I forgot, it happened once when I ran JFv1.41 RC30 and three times with RC33.
Happens to me too.
Happens here, too. I see it as the eccentricity of my little electronic brain.
happened a few times, bit annoying.
Happen to me 2 times since updated to rc33 1.41
Happened here too. I was just coming to see if anyone knows what's up, but I guess not yet. I'm running JF 1.41 RC33.
And here I was thinking I was the only one going nuts. It's weird because it did happen when I was on JFv1.41 RC30 as well.
i read a post on the tmobile forum that it could be the battery moving just slightly. i'll have to find the post again. They mentioned something about putting tape between the handset and the battery. Ill post if here when i find it.
http://forums.t-mobile.com/tmbl/board/message?board.id=87&message.id=28873&query.id=74936#M28873 here it is.
it's not that it's shutting off. it reboots. android.process error message
have you tried reflashing after a complete wipe?
this happens to me at times, but the wait option doesn't force close so i am ok with it.
yeah, i've done a wipe and reflash. we'll see how it goes.
but when it happens, it doesn't matter whether i press wait or force close, it does the same thing. reboot.
Edited original post. But the error message that pops up is android.process.acore. no clue to any of this.
did a wipe..solved the prob for me
Same here - moving from RC33 to ADP 1.1h w/o a wipe caused acore crashes.
Same here. I have my apps to SD card with JF 1.41 (soon 1.41 after the JFv1.42_RC33_MOD.zip finishes downloading) and a custom theme. I was assuming it had something to do with some of the app that was running in the background. However since I have over 100 apps stored to my sdcard it'll be pretty difficult to pinpont which one could be causing the problems (if any).
About half the time, when I try to answer an incoming call, my Verizon TP2 will only mute the ring without answering the call. It responds the same whether I use the touch screen to answer or press the send key, and whether or not the phone is locked or unlocked when the call arrives. Has anyone had a similar problem or know of a fix? Thanks.
I got this behavior the first time I finished getting the phone set up how I wanted. I eventually had to hard reset to fix it.
I think it was probably s2u2 interfering with the nonstandard dialer / answer bits on the phone. Even uninstalling it didn't help though. I have not bothered to try reinstalling s2u2 after the reset though to see if it causes the problem again.
i have this same problem. as i recall there was some registry tweak you could do to fix it, but i cant remember it to save my life. I have the worst problem with being on the internet and trying to answer a call. anyone know of a fix? whenever i am on opera and try to answer an incoming call it just freezes and i have to exit opera and call the person back. anyone with a fix for this other than a hard reset?
i had the same problem before i flashed to 6.5 on my vzw tp2. I also suspected that it was because of s2u2: I followed to uninstalling and i kept on getting a message about s2u2.exe not being a valid app or something. I also thought it could have been because of the dialer i had. The dusk dialer...for sense2.1 while i had manilla. after the flash i reinstalled s2u2, and will see if this persists to happen again.
It happened to me for the first tiem twice yesterday, my phone awoke and I could see my taskbar icon switch to 1x but I didn't see a call then I got a voicemail, when I called the person back they said it rang 6 times and went to voicemail, and it happened again later where i saw the call box and slide to answer come up but the screen was stuck and I couldn't answer it, not even with the hardware key.
Same thing is happening to me. The first time someone calls it won't answer whether I use the soft key or the hard key and the screen just freezes. However when the person calls back, it answers immediately when I click the answer button. I don't have S2U2 or any other phone/lock apps which interfere with answering a call.
Same here guys, I have been having the same issue, but as I can see for weeks now I haven't been able to nail down a solution either...
I too have had the same issue for several weeks. More prevalent when the screen is locked. Rings once and goes to voicemail.
stupid double post.
I've only run across this issue when I am using too much RAM. Try using cleanram and closing out tasks that you are not using.
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
reddington said:
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
Click to expand...
Click to collapse
have you tried s2u2 and their call answering interface?
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.
I have this weird issue since I've updated to OOS 10.01. When my phone is locked and I receive a phone call the screen flashes with the caller info for a second then goes back to the lock screen and then goes back to the caller info screen. This happens every time I receive a phone call when the phone is locked.
Any insights?
Thanks
Please help, any insights/suggestions?
This is driving me nuts
Thanks
Something causes this issue, I have not been able to pinpoint the cause. I tried stock and rooted OOS 10 but no difference. I experienced the problem with both setups. Does not happen after a fresh install, but after a while starts to happen all over again.
Anybody else experiencing the same problem ?
Thanks
OK just a short recap, haven't had the issue for a while now. Still trying to find the cause.
Things I did differently since the last full wipe:
- did not install viper4android
- did not enable call recording
- did not give "Auto Dark Mode" app write permissions via adb (this is the one I believe is the most likely candidate)