While in call, pressing the 'constact' button at the bottom right causes the following crash:
Unfortunately, the process com.android.phone has stopped
I would report in the [ROM]'s thread but I can't post there yet.
I'd appreciate if anyone would post it in that thread.
Also, if anyone has a solution I'd like to know.
Are there alternative com.android.phone that can be flashed?
ystavi said:
While in call, pressing the 'constact' button at the bottom right causes the following crash:
Unfortunately, the process com.android.phone has stopped
I would report in the [ROM]'s thread but I can't post there yet.
I'd appreciate if anyone would post it in that thread.
Also, if anyone has a solution I'd like to know.
Are there alternative com.android.phone that can be flashed?
Click to expand...
Click to collapse
I got the same force close error message, but my call continues when I click ok.
I have the CM9 dialer but it's the sense in call screen that gives you that message. Tell you the truth I never used the contact button until now. I usually go hit the home screen and hit my contacts from there.
And using another dialer like exdialer results the same, when in a call the in call screen is sense so you can't use the contacts button there either.
That isn't a bug in the ROM, it works fine on my phone with the same ROM.
You might try fixing permissions in CWM first, if not then try wiping and flashing again - make sure you follow all the instructions exactly and to the letter.
can you please link or give instructions for the
You might try fixing permissions in CWM first,
Click to expand...
Click to collapse
part?
Thanks.
ystavi said:
can you please link or give instructions for the
part?
Thanks.
Click to expand...
Click to collapse
You can try it, but it wont work. I have fixed my permissions countless times installing things lol.
Go to your recovery, and there,depending on what type of recovery you use, has the option to "fix permissions".
If you need additional info on that let me know.
Related
im on cynanogens latest and i am getting a force close almost everytime i exit and app. i searched but i dont know the exact way to fix my problem. thanks
nahanee20 said:
im on cynanogens latest and i am getting a force close almost everytime i exit and app. i searched but i dont know the exact way to fix my problem. thanks
Click to expand...
Click to collapse
Wipe and reflash. If that doesn't work flash the htc recovery image then cyanogen and see if that fixes it
Post in the thread of the ROM you are having problems with. Don't start a new thread. Thread closed.
Hi, I'm have an HTC EVO 3D with Sense 3.6 ICS 4.0.3 rom/ custom kernel, unlocked bootloader...
here is the sequence of my problem
superwipe
Install rom
install kernel
boot
rom works perfectly fine
restore user apps ONLY using TiBackup
system still works fine
reboot for any reason
continuous hot-reboots for ever
I'm sure some app or setting is cause that
but I want to know which by using a logcat
I know how to view logcats
but what should I look for?
there are too many values..
any help would be appreciated
thanks
Do you have fast boot checked under the Settings, Power? Try unchecking it before rebooting.
mf2112 said:
Do you have fast boot checked under the Settings, Power? Try unchecking it before rebooting.
Click to expand...
Click to collapse
never used fastboot before..
I always uncheck it because its usless
I just want to know what does an error causing a hot reboot looks like in logcat?
s_superman said:
never used fastboot before..
I always uncheck it because its usless
I just want to know what does an error causing a hot reboot looks like in logcat?
Click to expand...
Click to collapse
I understand, sorry I don't know how to read logcats better. The fast boot being turned seemed like the logical cause of the problem based on what you described. You might try posting in your devices Q&A forum instead of the General Q&A forum to get more device specific replies. Or you could try posting in the link in my sig for how to logcat and someone there may be able to help further.
typicaly in logcats (Eclipse for example) errors text is red color.
Try to see the lines before the reboot and target at the red ones
these lines will give you info about which app gives the error(if this is an app error) and what type of error it is.
even if you dont know how to handle the errors you see , try to unistall the app that gives the error , and see if the problem stops
I am trying to install NextGen 1.5
Problem is, in main menu, whenever I go to "recovery", fone gets struck with htc logo(white background). Then I have to take out battery, re-insert, press vol down+power up .....fast boot and run "recovery.bat" from pc(while connected fone to pc). then I get back the CWM Recovery Menu.
This is occuring everytime. Please help me to fix it.
Try with some other recovery, it's not like you don't have a choice And from which main menu you're getting in to recovery?
shortyoko said:
Try with some other recovery, it's not like you don't have a choice And from which main menu you're getting in to recovery?
Click to expand...
Click to collapse
well "main menu" refers to vol down+power button, which leads to "fast boot, recovery, factory reset" options.
Also u only suggest me some better recovery plz.
http://forum.xda-developers.com/showthread.php?t=2123503
I don't know if it's better or not, I'm still with the good old yannou's recovery, staying with the principle 'if it aint broke, don't fix it'
shortyoko said:
http://forum.xda-developers.com/showthread.php?t=2123503
I don't know if it's better or not, I'm still with the good old yannou's recovery, staying with the principle 'if it aint broke, don't fix it'
Click to expand...
Click to collapse
Thanks buddy...1 more thing, I hv installed nextgen1.5 Now when i go to music player-->sound enhancer..i get a FC, can u help me wid dis ?
Plus when i try to grant SU permission to any app..it says "Sorry, test failed. This feature cannot be granted to ur fone"
Fone is perfectly rooted. Had been using it for 1 yr, n now for the frst tym put custom rom and all these issues.
That's for the dsp
.Music player force closes bcoz of DSP libraries to fix just remove the library file from /system/lib/soundfx/libcyanogen-dsp.so it will perfectly like breeze.
Click to expand...
Click to collapse
For super user, enable usb debugging option from the phone menu(at the moment I don't remember where it was in the menu)
shortyoko said:
That's for the dsp
For super user, enable usb debugging option from the phone menu(at the moment I don't remember where it was in the menu)
Click to expand...
Click to collapse
Thanks a ton ! worked like charm ! +1
If u dont mind, tell me from where did u get that solution for music player ? I was looking for that but google dint help >_<
From NExtGen thread, when firstly 1.5 was released this was kind'a annoying bug, so there was a lot of question about that, here is the specific post from where I took it > http://forum.xda-developers.com/showthread.php?p=33599083&highlight=1+5+dsp+fix#post33599083
Just a friendly advice for the next time, there is a 'search in this thread' function which is really helpful when you have an issue with, whichever rom, cos it's possible for somebody to yell at you if you asked something that has been answered several times before
shortyoko said:
From NExtGen thread, when firstly 1.5 was released this was kind'a annoying bug, so there was a lot of question about that, here is the specific post from where I took it > http://forum.xda-developers.com/showthread.php?p=33599083&highlight=1+5+dsp+fix#post33599083
Just a friendly advice for the next time, there is a 'search in this thread' function which is really helpful when you have an issue with, whichever rom, cos it's possible for somebody to yell at you if you asked something that has been answered several times before
Click to expand...
Click to collapse
will keep that in mind thought google was more accurate, but oh well !
Help?
You got your answer bro, or still need help....
Sorry i checked PM today so didn't reply...:good:
artistaditya said:
You got your answer bro, or still need help....
Sorry i checked PM today so didn't reply...:good:
Click to expand...
Click to collapse
its fine, shortyoko helped me. You may edit the thread name with [solved] tag
try another custom rom
[Q&A] ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 1
Q&A for ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 10-30-14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for ★ ☆ [ROM][4.4.4] UnSenseSIX v1.01 | Sense/GPE/L | Hybrid | EYE | 10-30-14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I'm having a force close problem with Phone making the entire device inoperable. I'm not sure if it's a firmware problem because I don't know if I'm on the newest firmware. Can someone send me a link to the new firmware for fastboot flashing?
hk170 said:
I'm having a force close problem with Phone making the entire device inoperable. I'm not sure if it's a firmware problem because I don't know if I'm on the newest firmware. Can someone send me a link to the new firmware for fastboot flashing?
Click to expand...
Click to collapse
All error fixing info was posted by OP. It's the first post. You might be experiencing a simple problem of having to fix permissions in recovery through TWRP. Also, newest firmware is also listed wherever you downloaded it from, or use search to find it in another thread.
Sent via Tapatalk on my Big Red M8
hk170 said:
I'm having a force close problem with Phone making the entire device inoperable. I'm not sure if it's a firmware problem because I don't know if I'm on the newest firmware. Can someone send me a link to the new firmware for fastboot flashing?
Click to expand...
Click to collapse
Link to the latest firmware is in the OP.
It's the 3.28.605.4 (4.4.4) firmware.
I've confirmed that I have the updated firmware and the problem still persists. I flashed the insecure kernel to make it turn on. Fixing permissions did not solve anything. I am using twrp. Since that may be the issue, which recovery do you expect to have the best results?
Not really a question, more of an observation. I have done all the instructions from your inital post. I only get systemui FCs when my phone isnt on vibrate/silent. If i have volume up and receive an email or text then i get the fc. Not sure if you care, just something i noticed. Really like the look and feel.
If you wiped system, data, cache and dalvik before flashing, you should be able to fix the ui force closes using the method posted in my OP and post 3.
Boot to recovery, fix perms, wipe cache and dalvik, fix perms once more for good measure, reboot...
I don't need symptoms or causes.
Thanks.
The ROM can be run without that recurring annoyance, or it wouldn't have been worth my time posting.
Try what was said, if it doesn't work, try again, reflash, etc..
Still doesn't work, I can't help. Sorry
Appears to be a lost cause for the time being then which is unfortunate. Thanks for the response. Good luck with the development.
So I'm pretty sure I followed all directions properly but wifi is broken. I'm on Verizon and my h.boot is 3.19.0, my radio is 1.09.20.0702, firmware is 3.28.605.4.
Boots up normally fast, I've cleared cache and dalvik after fixing permissions. Dunno where I screwed up at.
rcanderson232 said:
Not really a question, more of an observation. I have done all the instructions from your inital post. I only get systemui FCs when my phone isnt on vibrate/silent. If i have volume up and receive an email or text then i get the fc. Not sure if you care, just something i noticed. Really like the look and feel.
Click to expand...
Click to collapse
Just posting to confirm that this did indeed work for me. I followed all of Santods instructions to a T and still had systemui FC's whenever i received a hangouts notification. Flipped my ringer mode to silent/vibrate and all of the sudden no systemui FC. Thanks for your post. hopefully more people can see this and try it out. Other than that one problem I was having, this ROM has been absolutely amazing. Best of both worlds!
Same.. Force close after following all the directions
Sent from my HTCM8
I'm having trouble booting into recovery. Since there is no APM, I power off and hold volume down and power and I just get a normal boot sequence, trying to boot into recovery from an app also does not work. I'm using TWRP 2.7.1.
mbtags said:
I'm having trouble booting into recovery. Since there is no APM, I power off and hold volume down and power and I just get a normal boot sequence, trying to boot into recovery from an app also does not work. I'm using TWRP 2.7.1.
Click to expand...
Click to collapse
Hold down the volume button and do a restart instead. Works better that way.
mbtags said:
I'm having trouble booting into recovery. Since there is no APM, I power off and hold volume down and power and I just get a normal boot sequence, trying to boot into recovery from an app also does not work. I'm using TWRP 2.7.1.
Click to expand...
Click to collapse
As soon as you hit restart..... And see the htc logo come on.... Hold volume down and power... Should take you to HBOOT screen... Then choose recovery
Has anyone been able to fix the notification FC's besides setting alerts to mute/vibrate?
detr0yt said:
As soon as you hit restart..... And see the htc logo come on.... Hold volume down and power... Should take you to HBOOT screen... Then choose recovery
Click to expand...
Click to collapse
As the post above you states, just volume down works fine and is simpler.
So as you said, wait to see HTC logo after hitting restart, then just press and hold volume down until hboot menu appears..
That is the simplest way to get to hboot/recovery.
ludeboy said:
Has anyone been able to fix the notification FC's besides setting alerts to mute/vibrate?
Click to expand...
Click to collapse
Quite a few folks have posted that they were able to fix them using my instructions.
And others have posted that the rom is running well for them, no force close issues.
So I would say yes, someone definitely has.
ludeboy said:
Has anyone been able to fix the notification FC's besides setting alerts to mute/vibrate?
Click to expand...
Click to collapse
We must be part of the unlucky few. Followed all of his instructions in the OP and still get the FC when im not on silent/vibrate. I have flashed several ROMs before and never had a problem with "following directions". Honestly, I never need to have my phone on sound, so I dont really care about the FC. It would just be nice to figure out what we are doing wrong. ROM is great and I think im definitely going to stay with this one for a while.
I literally have been trying for hours to get this to work... I have followed this to a 100% T and still no luck... Im clueless... After i had everything set up.. I removed my gmail account.. And all my text messages were perfect... I re added my gmail account and it started doing the forced closes all over again... So discouraged
santod040 said:
Quite a few folks have posted that they were able to fix them using my instructions.
And others have posted that the rom is running well for them, no force close issues.
So I would say yes, someone definitely has.
Click to expand...
Click to collapse
You're like seriously an angry dev or something dude. I'm trying to get help from others since you don't seem to want to help other than snapping and telling people to move along. You got a cool thing going and I'm just trying to make it work.
I tried doing what you said a million times and wiped my phone a million times. So I'm trying to see if those that have gotten to work have actually gotten it to work or just thought they did like I did by putting the phone on vibrate. And maybe if they got it to work, they have something specific like that they might want to share to help others out. Much like I did when I said you have to wipe the system partition. I realize now that you put that in your instructions, but most people don't wipe system when they flash ROMs. Was I stupid? Yes. Should I have followed instructions to a T? Yes. But after flashing ROMs for a while, you start to assume things.
---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------
detr0yt said:
I literally have been trying for hours to get this to work... I have followed this to a 100% T and still no luck... Im clueless... After i had everything set up.. I removed my gmail account.. And all my text messages were perfect... I re added my gmail account and it started doing the forced closes all over again... So discouraged
Click to expand...
Click to collapse
Did you reboot after you removed your gmail account? I just tried removing mine and still getting FC.
Basically, everytime i power on, it goes straight to setup (ive done a data wipe), hangs for 2 seconds, then reboots
again
and agaoin
and again
PLEASE HELP
this is on EVERY ROM
Ive even erased EVERYTHING and flashed stock cm11s images (https://cyngn.com/products/oneplusone/) bottom of the page
I hope this helps!
Have you tried this?
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
hamzahrmalik said:
Basically, everytime i power on, it goes straight to setup (ive done a data wipe), hangs for 2 seconds, then reboots
again
and agaoin
and again
PLEASE HELP
this is on EVERY ROM
Ive even erased EVERYTHING and flashed stock cm11s images (https://cyngn.com/products/oneplusone/) bottom of the page
Click to expand...
Click to collapse
Highly publicized error with One Plus my friend there are threads here related to it and on the web as it notated above. Do a little reading and its nothing more than a simple line of code to enter. Hope it works and fixes everything for you. Just remember to do some research in the future before posting
thecrab93 said:
Have you tried this?
http://www.androidpolice.com/2014/1...den-death-bug-results-neverending-boot-loops/
Click to expand...
Click to collapse
Worked thanks
playya said:
Highly publicized error with One Plus my friend there are threads here related to it and on the web as it notated above. Do a little reading and its nothing more than a simple line of code to enter. Hope it works and fixes everything for you. Just remember to do some research in the future before posting
Click to expand...
Click to collapse
Yeah I've seen it but I skimmed it I didn't think it was relevant, my bad
Sent from my amazingly awesome OnePlus One using Tapatalk