Hello,
So far Holic's ROM seems to be the only one without in-call volume problems on my Vivid (Bell Canada) but there are two problems, one more annoying than the other
first, most annoying problem: after I install, the phone will upgrade to the latest apps like Hangouts. Everything works great, I can start hangouts and chat.
But after some time (5 to 10 minutes) of the phone just sitting there, or especially after a reboot, I will get the "google play services is not supported by your device" error. I have to remove update to google play store and resintall it, and then problem goes away temporarily and hangouts is usable again, and after the next reboot same problems reappear.
Does anyone have any fix for this?
second problem, less annoying:
On the phone dialer, there is a button at the bottom right which looks like a button for calling voicemail (has some funny symbols on it)
if I press this button I get error message "Android.process.acore has stopped unexpectedly". Does anyone else have this?
My phone is S-ON
I reinstalled the rom several times. I do the full system wipe before from recovery, flash the boot image, install rom with WCX recovery, re-flash the boot image from the SD card
same problem every time.
tudorvictor said:
Hello,
So far Holic's ROM seems to be the only one without in-call volume problems on my Vivid (Bell Canada) but there are two problems, one more annoying than the other
first, most annoying problem: after I install, the phone will upgrade to the latest apps like Hangouts. Everything works great, I can start hangouts and chat.
But after some time (5 to 10 minutes) of the phone just sitting there, or especially after a reboot, I will get the "google play services is not supported by your device" error. I have to remove update to google play store and resintall it, and then problem goes away temporarily and hangouts is usable again, and after the next reboot same problems reappear.
Does anyone have any fix for this?
second problem, less annoying:
On the phone dialer, there is a button at the bottom right which looks like a button for calling voicemail (has some funny symbols on it)
if I press this button I get error message "Android.process.acore has stopped unexpectedly". Does anyone else have this?
My phone is S-ON
I reinstalled the rom several times. I do the full system wipe before from recovery, flash the boot image, install rom with WCX recovery, re-flash the boot image from the SD card
same problem every time.
Click to expand...
Click to collapse
What Gapps are you installing? Have you tried different ones?
CM11 in call volume is pretty much gone since about the middle of January (if you read the thread, you'll see good feedback about it from about the 15th on). Only issue is sending/recieving MMS. Might want to give it another shot since this seem to be the only one getting worked on by the devs.
Yuskow said:
What Gapps are you installing? Have you tried different ones?
CM11 in call volume is pretty much gone since about the middle of January (if you read the thread, you'll see good feedback about it from about the 15th on). Only issue is sending/recieving MMS. Might want to give it another shot since this seem to be the only one getting worked on by the devs.
Click to expand...
Click to collapse
I'm not flashing any Gapps on this, the ROM already comes with them.
This is a ROM based on 4.0.3 ICS, not kitkat
I actually tried two versions of CM11, one was the latest unofficial nightly build from february 19, and the other was the albinoman release from january 15. both have the low volume problem.
I also tried the Borked ROM, based on 4.0.3, and it has the same low call volume problem, but no other issues like hangouts not working.
What GApps should I flash for a 4.0.3 based ROM?
You don't flash gapps on a stock based ROM ever
Sent from my Vivid 4G using XDA Premium 4 mobile app
Related
When I try to enable WIFI on my G1, for a couple of seconds it says: enabling WIFI, but then the phone becomes unresponsive (for about 1 second) and it reboots.
IIRC the problem started when I upgraded to the new CynogenMod ROM (4.1.99, but not sure), but it doesn't seem to be linked to the ROM.
I have always used CyanogenMod and update with every new version.
I tried to go back to the default HTC rom, but this doesn't solve the issue.
Does anyone know what may cause this or give me some tips on how to debug this?
I tried to run 'adb logcat' but it shows no info.
The exception browser in the CyanogenMod is also empty.
I don't know what else I could try.
Some extra info:
HSPL 10.95.3000
Radio 2.22.19.26I
CynogenMod ROM 4.1.99 is not the newest. Wipe, flash the htc image, flash cyan's newest and try wifi again.
No, I know, but I think that's when the problems started.
Latest version I installed was 4.2.13
I have installed the RC7 dreaimg.nbh now (used to root the G1), and when I try to enable WIFI on this rom, the phone doesn't reboot, it keeps working, but I get an error saying that WIFI could not be started.
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
mattb3 said:
I'm also having problems with wifi causing random reboots. For me it usually happens once a day if wifi is enabled and not at all if its disabled. Once the phone reboots, it hangs at the android screen and I have to do a battery pull to reset it. The problem also appears to be rom independent. Very weird, it has started happening in the last few weeks and I can't think of anything that has changed.
Click to expand...
Click to collapse
This is consistent with my experience as well. By far, the VAST majority of spontaneous reboots that have occurred on my phone have been when using wifi. Some of the older Cyan ROMs were really bad about this, but this continues to occur (although much less frequently) regardless of the ROM. I am presently using SuperD and have had one reboot in the past week.
This seems to happen most often when using the wifi heavily; for instance, I get a reboot probably every 3rd or 4th time when I'm doing my weekly podcast downloads. I don't remember any reboots when just surfing the web or downloading apps, though.
I have never had this happen when I was running cyan.
Are you wiping everything? Even EXT and dalvick?
Are you using any other apps when this is running and rebooting? Perhaps an offending app?
You should also open ADB and run ADB Logcat and try to replicate the issue and try to get a log submitted so the dev can help determine what is causing this issue.
I wiped everything and even without any apps installed, it just reboots.
adb logcat doesn't show a thing when the phone reboots, it just exits.
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
have the exact same problem... can dial out no problem but only receiving calls. so thinking about whether I should flash another rom until this is fixed.....
I was wondering could I just do a factory reset and then flash the rom over again? Do I have to disable the voodo lagfix before? Not too sure how this works heh.
I don't have this problem. But whenever i am in the game "flick kick football," I get some random hangs, and is forced to close. I suspect that happens when I get incoming calls. Anyway to confirm this?
Jule1k said:
Hello
I just installed Darky's 5.2 ROM over my stock 2.1-update1 and everything works fine, but whenever I receive a call something (dialer?) gets a force close and the call is rejected together with a temp. loss of signal.
Then everything is back to normal...
Any steps I'd take? I'm pretty new to this.
Click to expand...
Click to collapse
I have the same problem. I recived a call, something force closed, the signal dropped and i lost the operator. I had similar problems with bluetooth and file manager before on this ROM, but I re-flashed it and everything worked again.
no problem here with Darky's 5.2 ROM and the Clean Guide Instruction, i just received a call without any problems
I used the easy guide and did not clean anything or do a factory reset, I just followed it like a dumbo. I came from 2.1-update1 stock JM5 kernel with a ton of apps installed, if that helps.
hey I think I found a solution to this. I went to recovery mode, wiped cache, wiped dalvik, did a factory reset and voila, receiving calls works without force closing.
phew.. was about to download another rom. anyhow, hope that works for you Jule!
still a few problems with the ROM that i encountered:
- my AT&T home button is not working.... not to sure whether there will ever be a fix for it
- media volume, even set to max, is not working when playing movies and youtube.
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
koolkeith said:
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
Click to expand...
Click to collapse
maybe your sim is faulty. try to get a new one from your provider. or it just has a bad contact in your phone.
about the lagging: did you try a clean flash? is your storage full? my phone gets pretty laggy when my storage is nearly full..
Hey thanks for your reply! However I dont think its the sim card, and as I mentioned I clean flashed several times with several twrp version and also twice with wiping all data on my sdcard...
Sorry if I can't offer a concrete solution, but I had similar issues (especially the first one, but also lag when switching networks) on my HOX+. Turns out it was the sim.
Try to test another sim before returning, and at least try a sense based rom. Since you say that it works without problem for a few days with Liquidsmooth 4.4, and then it starts breaking again, it may be rom (aosp?) related. But then again, it may be just random.
Hope you figure it out soon
Thanks akpe! I ordered a new sim card, if that doesnt help I suppose its something hardware related...
Well, the new sim card didnt help. My problem seem very similar to this: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/
Basically my whole radio disconnects and restarts itself when turning off wifi. Reading that androidpolice thread leads me to thinking about flashing an earlier firmware, from 4.2.2. I have no idea which one, or if I can use the one in that thread or not.
Any suggestions? I'd appreciate it, googling for hours and reading catlogs for days isnt getting me anywhere..
HELP!
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
akpe said:
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
Click to expand...
Click to collapse
Hi akpe! I took your advice and am now running ViperOne 7.0.2 and so far it WORKS! So it seems it was indeed that google bug. HUGE THANKS!
Is it possible to have the aosp lockscreen when at the same time using a pin? I can't seem to figure that out.
Thanks again!
Glad it worked
As for the lockscreen, no idea mate, I'm using the stock one :/ Ask around in the ViperOne thread, maybe someone there knows
Ok, thanks again!
Another thing I cant find is profiles? Need it to make whatsapp notification sound silent when listening to music..
Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
austtint said:
So for some reason today, my phone restarted and now I can't call people or receive calls, if I do. My phone restarts. Also can't use Bluetooth or it also does the same and restarts what can cause this? My phone getting too hot and damaged the motherboard? When I installed a kernel it was corrupted? I really have no understanding what caused this. I had resurrection from on it. I updated it with a newer one and did a bootloop. So I put cyangemod on it and worked but noticed those huge issues. Thinking the ROM was corrupted I put rr back on it and had the exact same issues. Any help would mean everything to me
Click to expand...
Click to collapse
How are you flashing your roms? Like, what sort of wipe, what flash order, etc.
Sent from my DROID Turbo using Tapatalk
for some reason after going back to stock which fixed everything, everytime I go back now to cm 13. I go to advance options under wiping and just check them all, and wipe. Then put the rom and gapps on then do the cache wipe. Then roboot. Afterwards, I still had the problem so I just went back to stock again.
Settings -> Apps -> gear icon -> Default Apps -> Phone app.
Make sure you set your Google Dialer to default, otherwise incoming and outgoing calls cause reboots.