I flashed my Redmi note 10 pro (global) a month ago and installed pixel experience then switched to Xiaomi.eu and both were working fine
, I then switched to MSMextended first blood and had a billion bugs(not receiving or sending sms, apps crashing, restarting after calls, etc..)
, after many failed Installations and buggy versions I managed to fix all of the bugs and installed derpfest v12 and everything is working properly except the random restarts and especially after missed calls the phone randomly reboots
I tried everything but this bug kept appearing in every custom rom I had so far and I can't see why
Any help is greatly appreciated bec I can't use my phone like this
Redminote10prorom said:
I flashed my Redmi note 10 pro (global) a month ago and installed pixel experience then switched to Xiaomi.eu and both were working fine
, I then switched to MSMextended first blood and had a billion bugs(not receiving or sending sms, apps crashing, restarting after calls, etc..)
, after many failed Installations and buggy versions I managed to fix all of the bugs and installed derpfest v12 and everything is working properly except the random restarts and especially after missed calls the phone randomly reboots
I tried everything but this bug kept appearing in every custom rom I had so far and I can't see why
Any help is greatly appreciated bec I can't use my phone like this
Click to expand...
Click to collapse
I too experiencing same thing after custom rom installation. To be more specific, First I installed PE 12 on my Asus max pro M2. I thought it was due to notification. So I disabled every notification. It seems to work for sometime, but the problem starts again. I thought it was ROM problem(Actually it was first time I flashed custom rom).So, This time I clean flashed new voltage OS rom. Again it has same problem. But randomly I observed that whenever I am in same signal eg only on 4G, the phone doesn't reboot. Whenever the phone changes from one signal to other( Eg 2G TO 3G OR TO 4G) it restarts. Yesterday, I locked it only on 2G. Since then I have not experienced any Random restarts. I think it is something to do it Carrier or Google Carrier service or anything.
JUST LOCK IT IN ANY ONE SIGNAL.
surya.mannadiar said:
I too experiencing same thing after custom rom installation. To be more specific, First I installed PE 12 on my Asus max pro M2. I thought it was due to notification. So I disabled every notification. It seems to work for sometime, but the problem starts again. I thought it was ROM problem(Actually it was first time I flashed custom rom).So, This time I clean flashed new voltage OS rom. Again it has same problem. But randomly I observed that whenever I am in same signal eg only on 4G, the phone doesn't reboot. Whenever the phone changes from one signal to other( Eg 2G TO 3G OR TO 4G) it restarts. Yesterday, I locked it only on 2G. Since then I have not experienced any Random restarts. I think it is something to do it Carrier or Google Carrier service or anything.
JUST LOCK IT IN ANY ONE SIGNAL.
Click to expand...
Click to collapse
Yes that's exactly it, whenever I'm on 4g and get a call it switches from 4g to 2g to make the call and then back it restarts, I have dual Sims so I'll leave one on 4g and lock the other on 2g and try this, ty
Redminote10prorom said:
Yes that's exactly it, whenever I'm on 4g and get a call it switches from 4g to 2g to make the call and then back it restarts, I have dual Sims so I'll leave one on 4g and lock the other on 2g and try this, ty
Click to expand...
Click to collapse
If you got any solution for this, let me know
I have faced this issue when I use Network signal guru to change network bands(Jio 4G) for better connection on a couple of custom roms on my moto g6. Fortunately it didn't happen anywhere else. Just bought Redmi note 10 pro, fingers crossed when I flash custom rom.
surya.mannadiar said:
I too experiencing same thing after custom rom installation. To be more specific, First I installed PE 12 on my Asus max pro M2. I thought it was due to notification. So I disabled every notification. It seems to work for sometime, but the problem starts again. I thought it was ROM problem(Actually it was first time I flashed custom rom).So, This time I clean flashed new voltage OS rom. Again it has same problem. But randomly I observed that whenever I am in same signal eg only on 4G, the phone doesn't reboot. Whenever the phone changes from one signal to other( Eg 2G TO 3G OR TO 4G) it restarts. Yesterday, I locked it only on 2G. Since then I have not experienced any Random restarts. I think it is something to do it Carrier or Google Carrier service or anything.
JUST LOCK IT IN ANY ONE SIGNAL.
Click to expand...
Click to collapse
THANK YOU!!
I was basically desperate after trying literally everything I could think of and like 5 different custom roms, but finally it's your solution that fixed it.
I have 2 Sims and Ik one of the carriers has a problem with 4g in my phone even on stock, once I set that one to 2g and the other 4g it hadn't restarted since
So ty
Related
Hello all,
I installed the official 2.03.404.2 NLD ROM on my HTC Touch Diamond.
(Radio version is 1.09.25.23). I didn't use the backup utility to restore my settings afterward, instead I installed my few applications by hand again.
I configured the phone to only use GSM, both to conserve power and costs (I have wifi both at home and in the office).
However, with this new ROM, often the phone becomes unresponsive to incoming calls. It happens often after the power management puts the phone to sleep whilst I have an active wi-fi connection using Opera.
People who try to call me then get my mailbox, even though the phone is ON and everything looks normal on the display. Crazy enough, the Diamond itself can make phone calls without problems, and then I'm immediately flooded with text messages from my provider telling me there are messages on my mailbox.
I now make dummy phone calls several times daily just to be sure the phone remains logged into the network, but this really sucks. Does anyone else experience this?
what network are you using?
T-mobile NL over GSM.
But the problem coincides with the installation of the new ROM.
I have exactly the same ROM / same Radio / same provider (T-Mobile NLD) as you have, and I don't have this problem (at least, not that I know off). I also have the phone in GSM mode almost always instead of 3G mode. So I think it's not a bug in the rom. However, there is already a newer rom available than the one we have, so maybe you could try upgrading to the latest?
I have ROM version: 1.93.720.2 WWE (Radio version: 1.00.25.07) on my HTC Diamond. I have never modified or upgraded my ROM. I face a similar kinda problem as yours. The only difference is that it happens once in a day and that too early morning. So I have to make a call to any no. to wake my phone up. This sounds funny but yeah I m facing this problem. Is it bcos of ROM version? Whats the latest ROM version for HTC Diamond? How can I update it? If I update ROM will I lose all my data. Please hlp I m new to this.
I m from India and using AIRTEL network over GSM.
@Suchit_g:
Early in the morning, you mean shortly
after pulling out the charger cable?
Sounds like a power management prob.
@Drazix: Thanks for the info about
the new ROM, I will try it out.
Hmm bobokonijn
Even I thought so but this happens even if my phone is not charging. I charge my phone once in two days but this happens almost every morning. The 1st call of the day should be made by me. If I fail to call, my callers get the unavailability message even if my phone is on and showing network signal bars. My phone starts working only and only if I use network (either call someone or use GPRS) for the 1st time in the morning and then for the rest of the day my phone works without any problems. Hope someone can help me out with this?
hi,
I am facing a problem with my kaiser.
I've been having it for 1 year now, changed lots of roms and was working perfectly.
Suddenly now i am facing problems with the phone.
I am having a full signal but when they call me most of the times it doesn't ring and after 4-5 minutes i receive a message from my provider that i have missed calls.
Also when i call someone the phone hangs up after 1-2 minutes of conversation.
There are times that is loosing signal, can't find network etc..
I am facing lot's of strange problems, i tried changing all kind of Radios and ROMs but nothing fixed this problem
Anybody has an idea?
Well, I know this isn't too helpful, but can you try your sim in another phone to see what happens?
Oh and can you share more about where you are and whats on your phone?
hi and thanks for your reply
i am from Cyprus using the CYTA-VODAFONE provider.
i have the PDAcorner Ultimate v2 ROM installed but as i have stated above, i have tried also other ROMS including the original rom that was originally installed on the phone.
What radio do you have installed?
i tried from 1.65 many version to 1.71..
finaly the local htc service center told me that the problem is with the power module chip, and that is not replaceable.
anybody knows if this is right?
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
Hey guys, Basically I live in Ireland and bought my friends nexus 6 when he got a new phone.
It was working great and I rooted 5.1.1 and when I saw The (only android 6.0 available) marshmallow update available on NRT I dirty-flashed it, after seeing a thread on reddit saying dirty flashing to marshmallow hadnt caused them any device defects
Had no complaints until I tried to call my sister today (admittedly the first call id made in the first two weeks of owning the phone) and it said "Sorry you don't have access to the service"
So I played around with some reboots and sim reinserting and was surprised to see that when I changed to 2g Mode, It could make the calls! Really strange, is there any chance that the marshmallow image released on NRT would've had bands specific to US carriers?
I can make calls via whatsapp for the time being I guess Lol, but if anyone could give me a headsup as to what I did wrong ( or even a solution) Id be pretty grateful!
Thanks,
Nick
wipe data/system then flash again. you should never dirty flash between 2 different android versions. and dont listen to anyone else, i bet they do have issues.
Thanks for the help but sadly this didnt work for me at all!
Was playing around last night after I reflashed and I went to system apps and on seeing telephone and phone (two seperate apps , normal?) I disabled 'phone' for a second and could place a call successfully over 3g - but obviously with no dialer interface whatsoever because the app was disabled. Ive rooted and custom flashed alot of my phones but this has me puzzled
I had this problem on a previous phone. What happened is that it was stuck on LTE only. I know this phone has volte, but try messing with mobile connection
I have a Pixel 4xl on Spectrum. Since my phone updated to Android 12 I have been unable to make phone calls on cellular and data randomly drops, you can watch it flash off and on several time, randomly. I get a Verizon error message. I can make calls on wifi only. After security and bug fix it worked for a short time then back to not working. My wife has the same phone and hers worked but dropped calls randomly anywhere between 1-10 minutes. Hers works a little better now but still has issues sometimes. After all this I rooted mine so I won't keep loosing data while working on it. In rooting I had to reinstall the factory ROM. I can now make calls on cellular but now drops calls between 1-10 minutes. Has anyone else seen this? Should I just go back to 11, if so which factory image do I use and how do I install it. I am rooted but not custom recovery installed.
iluvdroid said:
I have a Pixel 4xl on Spectrum. Since my phone updated to Android 12 I have been unable to make phone calls on cellular and data randomly drops, you can watch it flash off and on several time, randomly. I get a Verizon error message. I can make calls on wifi only. After security and bug fix it worked for a short time then back to not working. My wife has the same phone and hers worked but dropped calls randomly anywhere between 1-10 minutes. Hers works a little better now but still has issues sometimes. After all this I rooted mine so I won't keep loosing data while working on it. In rooting I had to reinstall the factory ROM. I can now make calls on cellular but now drops calls between 1-10 minutes. Has anyone else seen this? Should I just go back to 11, if so which factory image do I use and how do I install it. I am rooted but not custom recovery installed.
Click to expand...
Click to collapse
I seem to have faxed it. Contacted Spectrum for the second time and they had me reset the network settings and it seems to have fixed it. Settings->System->Reset options->Reset Wi-Fi, mobile & Bluetooth